No content-type specified when serving OAuth tokens to consumers
Bug #224462 reported by
Guilherme Salgado
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Neither /+request-token nor /+access-token specify the content-type of their responses, thus leaving that to be done by zope:
Content-Type: text/plain;
X-Content-
This should not be a big deal but it's probably a good idea to fix these pages to specify the content-type of their responses.
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
