Latest Version: 0.9.6.2

HTTPClientError

base class for the 400's, where the client is in-error

This is an error condition in which the client is presumed to be in-error. This is an expected problem, and thus is not considered a bug. A server-side traceback is not warranted. Unless specialized, this is a '400 Bad Request'


Attributes

a code

400

a comment

''

a detail

''

a explanation

'The server could not comply with the request since\r\nit is either malformed or otherwise incorrect.\r\n'

a template

'%(explanation)s\r\n<br/>%(detail)s\r\n<!-- %(comment)s -->'

a title

'Bad Request'

Methods

f __call__(self, environ, start_response, exc_info=None) ...

This exception as a WSGI application

f __getitem__(...) ...

f __init__(self, detail=None, headers=None, comment=None) ...

f html(self, environ) ...

text/html representation of the exception

f make_body(self, environ, template, escfunc, comment_escfunc=None) ...

f plain(self, environ) ...

text/plain representation of the exception

f prepare_content(self, environ) ...

f response(self, environ) ...

f wsgi_application(self, environ, start_response, exc_info=None) ...

This exception as a WSGI application

See the source for more information.

Top