Exceptions
This module implements a set of standard HTTP Errors as Python Exceptions.
Note: This code is mostly borrowed from werkzeug and adapted for circuits.web
Bases: exceptions.Exception
Baseclass for all HTTP exceptions. This exception can be called by WSGI applications to render a default error page or you can catch the subclasses of it independently and render nicer error messages.
Bases: circuits.web.exceptions.HTTPException
502 Bad Gateway
If you do proxying in your application you should return this status code if you received an invalid response from the upstream server it accessed in attempting to fulfill the request.
Bases: circuits.web.exceptions.HTTPException
400 Bad Request
Raise if the browser sends something to the application the application or server cannot handle.
Bases: circuits.web.exceptions.HTTPException
403 Forbidden
Raise if the user doesn’t have the permission for the requested resource but was authenticated.
Bases: circuits.web.exceptions.HTTPException
410 Gone
Raise if a resource existed previously and went away without new location.
Bases: circuits.web.exceptions.HTTPException
500 Internal Server Error
Raise if an internal server error occurred. This is a good fallback if an unknown error occurred in the dispatcher.
Bases: circuits.web.exceptions.HTTPException
411 Length Required
Raise if the browser submitted data but no Content-Length header which is required for the kind of processing the server does.
Bases: circuits.web.exceptions.HTTPException
405 Method Not Allowed
Raise if the server used a method the resource does not handle. For example POST if the resource is view only. Especially useful for REST.
The first argument for this exception should be a list of allowed methods. Strictly speaking the response would be invalid if you don’t provide valid methods in the header which you can do with that list.
Bases: circuits.web.exceptions.HTTPException
406 Not Acceptable
Raise if the server can’t return any content conforming to the Accept headers of the client.
Bases: circuits.web.exceptions.HTTPException
404 Not Found
Raise if a resource does not exist and never existed.
Bases: circuits.web.exceptions.HTTPException
501 Not Implemented
Raise if the application does not support the action requested by the browser.
Bases: circuits.web.exceptions.HTTPException
412 Precondition Failed
Status code used in combination with If-Match, If-None-Match, or If-Unmodified-Since.
Bases: circuits.web.exceptions.HTTPException
413 Request Entity Too Large
The status code one should return if the data submitted exceeded a given limit.
Bases: circuits.web.exceptions.HTTPException
408 Request Timeout
Raise to signalize a timeout.
Bases: circuits.web.exceptions.HTTPException
414 Request URI Too Large
Like 413 but for too long URLs.
Bases: circuits.web.exceptions.HTTPException
503 Service Unavailable
Status code you should return if a service is temporarily unavailable.
Bases: circuits.web.exceptions.HTTPException
401 Unauthorized
Raise if the user is not authorized. Also used if you want to use HTTP basic auth.
Bases: circuits.web.exceptions.HTTPException
raised by the request functions if they were unable to decode the incoming data properly.
Bases: circuits.web.exceptions.HTTPException
415 Unsupported Media Type
The status code returned if the server is unable to handle the media type the client transmitted.
none
none
none