Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • N node-http-proxy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 482
    • Issues 482
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • http ... PARTY!
  • node-http-proxy
  • Issues
  • #960
Closed
Open
Issue created Feb 13, 2016 by Administrator@rootContributor

Do not use "Transfer-Encoding: chunked" header for proxied DELETE requests (again)

Created by: Turbo87

This issue is related to PR #373 where this exact bug was already fixed by a89e2f26, but then later apparently introduced again by 8663ac1c.

The actual problem is that DELETE requests with both Content-Length: 0 and Transfer-Encoding: chunked are illegal and are being rejected by some servers (in this case nodejs since v0.10.42). If the incoming request only has the Transfer-Encoding header the proxy will somehow automatically set the Content-Length header to 0 but won't remove the encoding header which leads to this issue.

Assignee
Assign to
Time tracking