RESTful API is sending 400 for invalid tokens (should send 401)
Bug #751895 reported by
Natalia Bidart
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu One Servers |
Fix Released
|
High
|
Vincenzo Di Somma | ||
Bug Description
When sending a request with bad tokens, we're getting:
(400L, 'Invalid access token: hGTbRxOcMCaQqRH
As per the spec, we should send 401.
Revision history for this message
| Natalia Bidart (nataliabidart) wrote | #1 |
| Changed in ubuntuone-servers: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Ubuntu One web team (ubuntuone-web) |
| visibility: | private → public |
Revision history for this message
| Martin Albisetti (beuno) wrote | #2 |
| Changed in ubuntuone-servers: | |
| assignee: | Ubuntu One web team (ubuntuone-web) → Vincenzo Di Somma (vds) |
| Changed in ubuntuone-servers: | |
| status: | Triaged → In Progress |
| Changed in ubuntuone-servers: | |
| status: | In Progress → Fix Committed |
| Changed in ubuntuone-servers: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
As per http://
The server SHOULD return a 400 (Bad Request) status code when
receiving a request with unsupported parameters, an unsupported
signature method, missing parameters, or duplicated protocol
parameters. The server SHOULD return a 401 (Unauthorized) status
code when receiving a request with invalid client credentials, an
invalid or expired token, an invalid signature, or an invalid or used
nonce.