Confirmed users
36
edits
CloudServices/DataPipeline/HTTPEdgeServerSpecification: Difference between revisions
Jump to navigation
Jump to search
CloudServices/DataPipeline/HTTPEdgeServerSpecification (view source)
Revision as of 14:27, 18 March 2015
, 18 March 2015→POST/PUT Response codes: Format as a list
(→GET Response codes: Format as a list) |
(→POST/PUT Response codes: Format as a list) |
||
| Line 65: | Line 65: | ||
=== POST/PUT Response codes === | === POST/PUT Response codes === | ||
'''200''' - OK. Request accepted into the pipeline. | * '''200''' - OK. Request accepted into the pipeline. | ||
'''404''' - not found - POST/PUT to an unknown namespace | * '''404''' - not found - POST/PUT to an unknown namespace | ||
'''405''' - wrong request type (anything other than POST/PUT) | * '''405''' - wrong request type (anything other than POST/PUT) | ||
'''411''' - missing content-length header | * '''411''' - missing content-length header | ||
'''413''' - request body too large (Note that if we have badly-behaved clients that retry on 4XX, we should send back 202 on body/path too long). | * '''413''' - request body too large (Note that if we have badly-behaved clients that retry on 4XX, we should send back 202 on body/path too long). | ||
'''414''' - request path too long (See above) | * '''414''' - request path too long (See above) | ||
'''500''' - internal error | * '''500''' - internal error | ||
== Forwarding to S3 == | == Forwarding to S3 == | ||