Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-6947

POST service webhook Content-Encoding header

XMLWordPrintable

      The Stash Web Post Hooks Plugin sends a header

      Content-Encoding: UTF-8

      UTF-8 is not a valid content-encoding but a content-type.

            [BSERV-6947] POST service webhook Content-Encoding header

            Tarun Pereira added a comment -

            I have reported a bug against Atlassian and they have created a ticket against this, please vote on this issue to increase its priority: https://jira.atlassian.com/browse/FE-5658

            Tarun Pereira added a comment - I have reported a bug against Atlassian and they have created a ticket against this, please vote on this issue to increase its priority: https://jira.atlassian.com/browse/FE-5658

            Chason Choate added a comment -

            For anyone running into this issue, you can easily setup an nginx proxy to strip the "Content-Encoding" header. Here's what i'm using:

            server {
        listen 9001;
        server_name hubot_encoding_strip;

        location / {
                proxy_set_header Content-Encoding "";
                proxy_set_header Host $host:$server_port;
                proxy_pass       http://127.0.0.1:9000;
        }
}

            Chason Choate added a comment - For anyone running into this issue, you can easily setup an nginx proxy to strip the "Content-Encoding" header. Here's what i'm using: server { listen 9001; server_name hubot_encoding_strip; location / { proxy_set_header Content-Encoding ""; proxy_set_header Host $host:$server_port; proxy_pass http: //127.0.0.1:9000; } }

            Chason Choate added a comment -

            +1 I'm seeing this error with my hubot instance as well.

            Chason Choate added a comment - +1 I'm seeing this error with my hubot instance as well.

            Mark Healey added a comment -

            I just discovered this today when building a Node.js script listening for the webhook POST. The npm `body-parser` correctly chokes on this with an error:

            `Error: unsupported content encoding "utf-8"`

            Anyone looking at this?

            Mark Healey added a comment - I just discovered this today when building a Node.js script listening for the webhook POST. The npm `body-parser` correctly chokes on this with an error: `Error: unsupported content encoding "utf-8"` Anyone looking at this?

            Andreas Heumaier added a comment -

            Any Updates on this ?

            Andreas Heumaier added a comment - Any Updates on this ?

              khughes@atlassian.com Kristy
              jan.jungmann Jan Jungmann
              Affected customers:
              8 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: