Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 119
    • Issues 119
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • pikelang
  • pikepike
  • Issues
  • #5936

Closed
Open
Created May 03, 2011 by Peter Bortas@zinoOwner

Protocols.HTTP sometimes lack Content-Length header

Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=5936

Reported by Tobias Liin liin@roxen.com

--- Test case ---

[&var.status;]

=> [411]

Running the server with HTTP_QUERY_DEBUG shows that there is no Content-Length header declared in the request.

--- Test case 2 ---

[&var.status;]

=> [200]

With a message body the request now includes a Content-Length header.

Perhaps Protocols.HTTP should do Content-Length: 0 for empty http message bodies?

(by the way, insert#href does Query.async_request())

Assignee
Assign to
Time tracking