Closed
Bug 759899
Opened 14 years ago
Closed 14 years ago
Use 415 Unsupported Media Type in AITC Server
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gps, Assigned: rfkelly)
Details
(Whiteboard: [qa?])
Attachments
(1 file)
|
1009 bytes,
patch
|
telliott
:
review+
|
Details | Diff | Splinter Review |
I'm not sure if bug 747494 didn't get ported over to AITC, but in test_that_uploading_invalid_json_gives_a_400_response in the functional test suite, the first test uploads with Content-Type application/x-www-form-urlencoded by default. It expects a 400. I would expect the server to return a 415 per the spec.
|
Assignee | |
Comment 1•14 years ago
|
||
Ah, the AITC server parses the request before it gets to the underlying SyncStorage controller, so the 415 handling wasn't being applied. Patch copies it over.
As part of a larger refactoring I am going to be moving this logic into a cornice validator, but that's not ready yet.
Assignee: nobody → rfkelly
Attachment #628540 -
Flags: review?(telliott)
|
||
Updated•14 years ago
|
Attachment #628540 -
Flags: review?(telliott) → review+
|
|
Assignee | |
Comment 2•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
|
||
Updated•14 years ago
|
Whiteboard: [qa?]
|
||
Updated•3 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•