Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-12673

Remove the content-length header HTTP response

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      This appears to be breaking applications with invalid responses: https://github.com/nodegit/nodegit/issues/911

      #!python

[Error: HTTP parser error: unexpected content-length header]

      We realize this might break Bamboo Cloud functionality, but it's more than likely an easy fix on our end. Let's keep this ticket a placeholder so we can have people subscribe to any updates involving this

            [BCLOUD-12673] Remove the content-length header HTTP response

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3538106 ] New: JAC Suggestion Workflow 3 [ 3591873 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Jesse Yowell (Inactive) made changes -
            Status Original: GATHERING INTEREST [ 11772 ] New: RESOLVED [ 5 ]

            Jesse Yowell (Inactive) added a comment -

            We removed the content-length header response over the weekend

            Jesse Yowell (Inactive) added a comment - We removed the content-length header response over the weekend

            Jim Redmond (Inactive) added a comment -

            @tbranyen Unfortunately, that isn't really feasible. We're only adding the Content-Length header to responses for certain Git client requests, but those requests don't include a Referer header.

            Jim Redmond (Inactive) added a comment - @tbranyen Unfortunately, that isn't really feasible. We're only adding the Content-Length header to responses for certain Git client requests, but those requests don't include a Referer header.

            Legacy Bitbucket Cloud User (Inactive) added a comment -

            Are you unable to toggle this behavior based on referrer? I'd imagine it's feasible to maintain the content-length header for your Bamboo Cloud integration, but for everyone else who maintains spec compliance, would not get the header.

            Legacy Bitbucket Cloud User (Inactive) added a comment - Are you unable to toggle this behavior based on referrer? I'd imagine it's feasible to maintain the content-length header for your Bamboo Cloud integration, but for everyone else who maintains spec compliance, would not get the header.

            aed7 added a comment -

            Related:

            https://github.com/nodejs/http-parser/issues/289

            https://github.com/nodegit/nodegit/issues/911

            aed7 added a comment - Related: https://github.com/nodejs/http-parser/issues/289 https://github.com/nodegit/nodegit/issues/911
            Geoff created issue -

              Unassigned Unassigned
              jyowell Jesse Yowell (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: