OPTIONS http request gives spaces instead of commas in "Allow" header
Bug #1717682 reported by
Hanno Böck
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
The HTTPS OPTIONS method allows to query a server for the supported HTTP methods. The server is supposed to reply with an "Allow" header with a comma-separated list. However the launchpad server gives a space-separated list.
Example:
curl -sI -X OPTIONS https:/
gives output:
Allow: GET HEAD POST
For a correct server:
curl -sI -X OPTIONS https:/
gives:
Allow: GET, HEAD, OPTIONS
I can't judge where the bug is, as I don't know how the infrastructure of launchpad.net works. It may be a bug in a load balancer or proxy in front of the real software.
Related branches
lp:~cjwatson/launchpad/allow-header-syntax
- William Grant: Approve (code)
-
Diff: 25 lines (+2/-2)2 files modifiedlib/lp/services/webapp/doc/webapp-publication.txt (+1/-1)
lib/lp/services/webapp/servers.py (+1/-1)
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → Colin Watson (cjwatson) |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #2 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
Revision history for this message
| Colin Watson (cjwatson) wrote | #3 |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks. It's in the Launchpad codebase itself, in fact. I'll get it fixed.