B `-@sRdZddlZddlmZddlmZddlmZddl m Z ddl m Z ddl mZdd lmZd d Ze e Gd d d eeZeZGdddeZGdddeZGdddeZGdddeZGdddeZGdddeZGdddeZGdddeZGdddeZGd d!d!eZGd"d#d#eZGd$d%d%eZ Gd&d'd'eZ!Gd(d)d)eZ"Gd*d+d+eZ#Gd,d-d-eZ$Gd.d/d/eZ%Gd0d1d1eZ&Gd2d3d3eZ'Gd4d5d5eZ(Gd6d7d7e(Z)Gd8d9d9e(Z*Gd:d;d;e(Z+Gdd?d?e(Z-Gd@dAdAe(Z.GdBdCdCe(Z/GdDdEdEe(Z0GdFdGdGe(Z1GdHdIdIe(Z2GdJdKdKe(Z3GdLdMdMe(Z4GdNdOdOe(Z5GdPdQdQe(Z6GdRdSdSe(Z7GdTdUdUe(Z8GdVdWdWe(Z9GdXdYdYe(Z:GdZd[d[e(Z;Gd\d]d]e(ZGdbdcdce(Z?Gdddedee(Z@GdfdgdgeZAGdhdidieAZBGdjdkdkeAZCGdldmdmeAZDGdndodoeAZEGdpdqdqeAZFGdrdsdseAZGGdtdudueAZHdvdwZIdxdyZJiZKdZLxheMeNOD]V\ZPZQeReQeSreTeQereQe(eAhkrePUdzseVeQd{dZLeLreQeKeL<qW[P[Q[LdS)|a HTTP Exceptions --------------- This module contains Pyramid HTTP exception classes. Each class relates to a single HTTP status code. Each class is a subclass of the :class:`~HTTPException`. Each exception class is also a :term:`response` object. Each exception class has a status code according to :rfc:`2068` or :rfc:`7538`: codes with 100-300 are not really errors; 400s are client errors, and 500s are server errors. Exception HTTPException HTTPSuccessful * 200 - HTTPOk * 201 - HTTPCreated * 202 - HTTPAccepted * 203 - HTTPNonAuthoritativeInformation * 204 - HTTPNoContent * 205 - HTTPResetContent * 206 - HTTPPartialContent HTTPRedirection * 300 - HTTPMultipleChoices * 301 - HTTPMovedPermanently * 302 - HTTPFound * 303 - HTTPSeeOther * 304 - HTTPNotModified * 305 - HTTPUseProxy * 307 - HTTPTemporaryRedirect * 308 - HTTPPermanentRedirect HTTPError HTTPClientError * 400 - HTTPBadRequest * 401 - HTTPUnauthorized * 402 - HTTPPaymentRequired * 403 - HTTPForbidden * 404 - HTTPNotFound * 405 - HTTPMethodNotAllowed * 406 - HTTPNotAcceptable * 407 - HTTPProxyAuthenticationRequired * 408 - HTTPRequestTimeout * 409 - HTTPConflict * 410 - HTTPGone * 411 - HTTPLengthRequired * 412 - HTTPPreconditionFailed * 413 - HTTPRequestEntityTooLarge * 414 - HTTPRequestURITooLong * 415 - HTTPUnsupportedMediaType * 416 - HTTPRequestRangeNotSatisfiable * 417 - HTTPExpectationFailed * 422 - HTTPUnprocessableEntity * 423 - HTTPLocked * 424 - HTTPFailedDependency * 428 - HTTPPreconditionRequired * 429 - HTTPTooManyRequests * 431 - HTTPRequestHeaderFieldsTooLarge HTTPServerError * 500 - HTTPInternalServerError * 501 - HTTPNotImplemented * 502 - HTTPBadGateway * 503 - HTTPServiceUnavailable * 504 - HTTPGatewayTimeout * 505 - HTTPVersionNotSupported * 507 - HTTPInsufficientStorage HTTP exceptions are also :term:`response` objects, thus they accept most of the same parameters that can be passed to a regular :class:`~pyramid.response.Response`. Each HTTP exception also has the following attributes: ``code`` the HTTP status code for the exception ``title`` remainder of the status line (stuff after the code) ``explanation`` a plain-text explanation of the error message that is not subject to environment or header substitutions; it is accessible in the template via ${explanation} ``detail`` a plain-text message customization that is not subject to environment or header substitutions; accessible in the template via ${detail} ``body_template`` a ``String.template``-format content fragment used for environment and header substitution; the default template includes both the explanation and further detail provided in the message. Each HTTP exception accepts the following parameters, any others will be forwarded to its :class:`~pyramid.response.Response` superclass: ``detail`` a plain-text override of the default ``detail`` ``headers`` a list of (k,v) header pairs, or a dict, to be added to the response; use the content_type='application/json' kwarg and other similar kwargs to to change properties of the response supported by the :class:`pyramid.response.Response` superclass ``comment`` a plain-text additional information which is usually stripped/hidden for end-users ``body_template`` a ``string.Template`` object containing a content fragment in HTML that frames the explanation and further detail ``body`` a string that will override the ``body_template`` and be used as the body of the response. Substitution of response headers into template values is always performed. Substitution of WSGI environment values is performed if a ``request`` is passed to the exception's constructor. The subclasses of :class:`~_HTTPMove` (:class:`~HTTPMultipleChoices`, :class:`~HTTPMovedPermanently`, :class:`~HTTPFound`, :class:`~HTTPSeeOther`, :class:`~HTTPUseProxy`, :class:`~HTTPTemporaryRedirect`, and :class: `~HTTPPermanentRedirect) are redirections that require a ``Location`` field. Reflecting this, these subclasses have one additional keyword argument: ``location``, which indicates the location to which to redirect. N)Template) html_escape)create_accept_header) implementer)IExceptionResponse)Response)text_cCs8|dkr dSt|ts4t|tr,t|d}nt|}|S)Nzutf-8) isinstancestrbytesr)valuer^/home/kop/projects/devel/pgwui/test_venv/lib/python3.7/site-packages/pyramid/httpexceptions.py _no_escapes   rc@sneZdZdZdZdZedZedZedZ dZ dd d Z d d Z d dZ ddZeddZeZddZdS) HTTPExceptioniz Unknown Errorr z3${explanation}${br}${br} ${detail} ${html_comment} z${status} ${body}zj ${status}

${status}

${body} FNcKsd|j|jf}tj|fd|i|t||||_|_|rN|j|||_ |dk rl||_ t ||_ |dk rz||_ |jr|`|`dS)Nz%s %sstatus)codetitler__init__ Exceptiondetailmessageheadersextendcomment body_templaterbody_template_obj_json_formatter empty_body content_typecontent_length)selfrrrrZjson_formatterkwrrrrrs     zHTTPException.__init__cCs|jrt|jS|jS)N)rr explanation)r"rrr__str__szHTTPException.__str__cCs|||jdS)N)rrr)r)r"rbodyrenvironrrrrszHTTPException._json_formattercs|js|jsd}|jpd}dd}t|}|ddg}dd|Ddg}|d}|dkrd|_t}|j} d } |rd ||}nd|dkrd|_d|_ t }d } |r||}Gfd d d } | |} n d|_t }|j } d } |r||}| ||j ||j pd|||d} |j} tj| k rx<D]0\}}|dsRd|krRq0||| |<q0Wx(|jD]\}}||| |<qpW| | }| j|j|d}t|tr||j r|j nd}|g|_||_dS)Nr Z HTTP_ACCEPTz text/htmlzapplication/jsoncSsg|] }|dqS)rr).0Zofferrrr sz)HTTPException.prepare..z text/plainrz
z  cs eZdZddZfddZdS)z/HTTPException.prepare..JsonPageTemplatecSs ||_dS)N)excobj)r"r+rrrrsz8HTTPException.prepare..JsonPageTemplate.__init__cs"|jj|||jjd}t|S)N)rr&rr')r+rrjsondumps)r"rr&Zjsonbody)r'rr substitutes z:HTTPException.prepare..JsonPageTemplate.substituteN)__name__ __module__ __qualname__rr.r)r'rrJsonPageTemplatesr2)brr$rr html_commentzwsgi..)rr&zUTF-8)Zhas_bodyrrgetrZacceptable_offersr _html_escapehtml_template_objcharsetrplain_template_objr$rrritems startswithrlowerr.rr r encodeZapp_iterr&)r"r'r4rZ accept_valueacceptZ acceptablematchescapeZ page_templater3r2argsZ body_tmplkvr&pager)r'rpreparesd       zHTTPException.preparecCs|S)Nr)r"rrr wsgi_responseHszHTTPException.wsgi_responsecCs||t|||S)N)rFr__call__)r"r'Zstart_responserrrrHOs zHTTPException.__call__)NNNNN)r/r0r1rrr$rrr:r8rrr%rrFpropertyrG exceptionrHrrrrrs*!  L rc@seZdZdZdS) HTTPErrorz base class for exceptions with status codes in the 400s and 500s This is an exception which indicates that an error has occurred, and that any work in progress should not be committed. N)r/r0r1__doc__rrrrrK^srKc@seZdZdZdS)HTTPRedirectiona0 base class for exceptions with status codes in the 300s (redirections) This is an abstract base class for 3xx redirection. It indicates that further action needs to be taken by the user agent in order to fulfill the request. It does not necessarily signal an error condition. N)r/r0r1rLrrrrrMgsrMc@seZdZdZdS)HTTPSuccessfulz\ Base class for exceptions with status codes in the 200s (successful responses) N)r/r0r1rLrrrrrNrsrNc@seZdZdZdZdZdS)HTTPOkzw subclass of :class:`~HTTPSuccessful` Indicates that the request has succeeded. code: 200, title: OK OKN)r/r0r1rLrrrrrrrO~srOc@seZdZdZdZdZdS) HTTPCreatedz subclass of :class:`~HTTPSuccessful` This indicates that request has been fulfilled and resulted in a new resource being created. code: 201, title: Created CreatedN)r/r0r1rLrrrrrrrRsrRc@seZdZdZdZdZdZdS) HTTPAcceptedz subclass of :class:`~HTTPSuccessful` This indicates that the request has been accepted for processing, but the processing has not been completed. code: 202, title: Accepted Acceptedz'The request is accepted for processing.N)r/r0r1rLrrr$rrrrrUsrUc@seZdZdZdZdZdS)HTTPNonAuthoritativeInformationa) subclass of :class:`~HTTPSuccessful` This indicates that the returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. code: 203, title: Non-Authoritative Information zNon-Authoritative InformationN)r/r0r1rLrrrrrrrXs rXc@seZdZdZdZdZdZdS) HTTPNoContentz subclass of :class:`~HTTPSuccessful` This indicates that the server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. code: 204, title: No Content z No ContentTN)r/r0r1rLrrrrrrrrZs rZc@seZdZdZdZdZdZdS)HTTPResetContentz subclass of :class:`~HTTPSuccessful` This indicates that the server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. code: 205, title: Reset Content z Reset ContentTN)r/r0r1rLrrrrrrrr\s r\c@seZdZdZdZdZdS)HTTPPartialContentz subclass of :class:`~HTTPSuccessful` This indicates that the server has fulfilled the partial GET request for the resource. code: 206, title: Partial Content zPartial ContentN)r/r0r1rLrrrrrrr^sr^cs.eZdZdZdZedZdfdd ZZS) _HTTPMovea redirections which require a Location field Since a 'Location' header is a required attribute of 301, 302, 303, 305 and 307 (but not 304), this base class provides the mechanics to make this easy. You must provide a ``location`` keyword argument. zThe resource has been moved toz]${explanation} ${location}; you should be redirected automatically. ${detail} ${html_comment}r Nc s2|dkrtdtjf|||||d|dS)Nz.HTTP redirects need a location to redirect to.)rrrrlocation) ValueErrorsuperr)r"rarrrrr#) __class__rrr s z_HTTPMove.__init__)r NNNN) r/r0r1rLr$rrr __classcell__rr)rdrr`s r`c@seZdZdZdZdZdS)HTTPMultipleChoicesa subclass of :class:`~_HTTPMove` This indicates that the requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information is being provided so that the user can select a preferred representation and redirect its request to that location. code: 300, title: Multiple Choices i,zMultiple ChoicesN)r/r0r1rLrrrrrrrf!s rfc@seZdZdZdZdZdS)HTTPMovedPermanentlya subclass of :class:`~_HTTPMove` This indicates that the requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. code: 301, title: Moved Permanently i-zMoved PermanentlyN)r/r0r1rLrrrrrrrg2s rgc@seZdZdZdZdZdZdS) HTTPFoundz subclass of :class:`~_HTTPMove` This indicates that the requested resource resides temporarily under a different URI. code: 302, title: Found i.FoundzThe resource was found atN)r/r0r1rLrrr$rrrrrhAsrhc@seZdZdZdZdZdS) HTTPSeeOtherz subclass of :class:`~_HTTPMove` This indicates that the response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. code: 303, title: See Other i/z See OtherN)r/r0r1rLrrrrrrrjRs rjc@seZdZdZdZdZdZdS)HTTPNotModifieda subclass of :class:`~HTTPRedirection` This indicates that if the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. code: 304, title: Not Modified i0z Not ModifiedTN)r/r0r1rLrrrrrrrrkas rkc@seZdZdZdZdZdZdS) HTTPUseProxyz subclass of :class:`~_HTTPMove` This indicates that the requested resource MUST be accessed through the proxy given by the Location field. code: 305, title: Use Proxy i1z Use Proxyz8The resource must be accessed through a proxy located atN)r/r0r1rLrrr$rrrrrlrsrlc@seZdZdZdZdZdS)HTTPTemporaryRedirectz subclass of :class:`~_HTTPMove` This indicates that the requested resource resides temporarily under a different URI. code: 307, title: Temporary Redirect i3zTemporary RedirectN)r/r0r1rLrrrrrrrmsrmc@seZdZdZdZdZdS)HTTPPermanentRedirectz subclass of :class:`~_HTTPMove` This indicates that the requested resource resides permanently under a different URI and that the request method must not be changed. code: 308, title: Permanent Redirect i4zPermanent RedirectN)r/r0r1rLrrrrrrrns rnc@seZdZdZdZdZdS)HTTPClientErrora7 base class for the 400s, 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' iz Bad RequestN)r/r0r1rLrrrrrrrosroc@seZdZdZdZdS)HTTPBadRequestz subclass of :class:`~HTTPClientError` This indicates that the body or headers failed validity checks, preventing the server from being able to continue processing. code: 400, title: Bad Request zaThe server could not comply with the request since it is either malformed or otherwise incorrect.N)r/r0r1rLr$rrrrrpsrpc@seZdZdZdZdZdZdS)HTTPUnauthorizedz subclass of :class:`~HTTPClientError` This indicates that the request requires user authentication. code: 401, title: Unauthorized i UnauthorizedzThis server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.N)r/r0r1rLrrr$rrrrrqsrqc@seZdZdZdZdZdZdS)HTTPPaymentRequiredzW subclass of :class:`~HTTPClientError` code: 402, title: Payment Required izPayment Requiredz(Access was denied for financial reasons.N)r/r0r1rLrrr$rrrrrssrsc@s&eZdZdZdZdZdZdddZdS) HTTPForbiddenaT subclass of :class:`~HTTPClientError` This indicates that the server understood the request, but is refusing to fulfill it. code: 403, title: Forbidden Raise this exception within :term:`view` code to immediately return the :term:`forbidden view` to the invoking user. Usually this is a basic ``403`` page, but the forbidden view can be customized as necessary. See :ref:`changing_the_forbidden_view`. A ``Forbidden`` exception will be the ``context`` of a :term:`Forbidden View`. This exception's constructor treats two arguments specially. The first argument, ``detail``, should be a string. The value of this string will be used as the ``message`` attribute of the exception object. The second special keyword argument, ``result`` is usually an instance of :class:`pyramid.security.Denied` or :class:`pyramid.authorization.ACLDenied` each of which indicates a reason for the forbidden error. However, ``result`` is also permitted to be just a plain boolean ``False`` object or ``None``. The ``result`` value will be used as the ``result`` attribute of the exception object. It defaults to ``None``. The :term:`Forbidden View` can use the attributes of a Forbidden exception as necessary to provide extended information in an error report shown to a user. i Forbiddenz#Access was denied to this resource.NcKs&tj|f||||d|||_dS)N)rrrr)rorresult)r"rrrrrvr#rrrrs zHTTPForbidden.__init__)NNNNN)r/r0r1rLrrr$rrrrrrts rtc@seZdZdZdZdZdZdS) HTTPNotFounda subclass of :class:`~HTTPClientError` This indicates that the server did not find anything matching the Request-URI. code: 404, title: Not Found Raise this exception within :term:`view` code to immediately return the :term:`Not Found View` to the invoking user. Usually this is a basic ``404`` page, but the Not Found View can be customized as necessary. See :ref:`changing_the_notfound_view`. This exception's constructor accepts a ``detail`` argument (the first argument), which should be a string. The value of this string will be available as the ``message`` attribute of this exception, for availability to the :term:`Not Found View`. iz Not Foundz The resource could not be found.N)r/r0r1rLrrr$rrrrrw"srwc@s eZdZdZdZdZedZdS)HTTPMethodNotAllowedz subclass of :class:`~HTTPClientError` This indicates that the method specified in the Request-Line is not allowed for the resource identified by the Request-URI. code: 405, title: Method Not Allowed izMethod Not AllowedzSThe method ${REQUEST_METHOD} is not allowed for this resource. ${br}${br} ${detail}N)r/r0r1rLrrrrrrrrrx;s rxc@seZdZdZdZdZdS)HTTPNotAcceptablea3 subclass of :class:`~HTTPClientError` This indicates the resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request. code: 406, title: Not Acceptable izNot AcceptableN)r/r0r1rLrrrrrrryQs ryc@seZdZdZdZdZdZdS)HTTPProxyAuthenticationRequiredz subclass of :class:`~HTTPClientError` This is similar to 401, but indicates that the client must first authenticate itself with the proxy. code: 407, title: Proxy Authentication Required izProxy Authentication Requiredz,Authentication with a local proxy is needed.N)r/r0r1rLrrr$rrrrrzdsrzc@seZdZdZdZdZdZdS)HTTPRequestTimeoutz subclass of :class:`~HTTPClientError` This indicates that the client did not produce a request within the time that the server was prepared to wait. code: 408, title: Request Timeout izRequest TimeoutzHThe server has waited too long for the request to be sent by the client.N)r/r0r1rLrrr$rrrrr{ssr{c@seZdZdZdZdZdZdS) HTTPConflictz subclass of :class:`~HTTPClientError` This indicates that the request could not be completed due to a conflict with the current state of the resource. code: 409, title: Conflict iConflictz:There was a conflict when trying to complete your request.N)r/r0r1rLrrr$rrrrr|sr|c@seZdZdZdZdZdZdS)HTTPGonez subclass of :class:`~HTTPClientError` This indicates that the requested resource is no longer available at the server and no forwarding address is known. code: 410, title: Gone iGonezFThis resource is no longer available. No forwarding address is given.N)r/r0r1rLrrr$rrrrr~sr~c@seZdZdZdZdZdZdS)HTTPLengthRequiredz subclass of :class:`~HTTPClientError` This indicates that the server refuses to accept the request without a defined Content-Length. code: 411, title: Length Required izLength RequiredzContent-Length header required.N)r/r0r1rLrrr$rrrrrsrc@seZdZdZdZdZdZdS)HTTPPreconditionFailedz subclass of :class:`~HTTPClientError` This indicates that the precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. code: 412, title: Precondition Failed izPrecondition FailedzRequest precondition failed.N)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdZdS)HTTPRequestEntityTooLargea subclass of :class:`~HTTPClientError` This indicates that the server is refusing to process a request because the request entity is larger than the server is willing or able to process. code: 413, title: Request Entity Too Large izRequest Entity Too Largez7The body of your request was too large for this server.N)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdZdS)HTTPRequestURITooLongz subclass of :class:`~HTTPClientError` This indicates that the server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. code: 414, title: Request-URI Too Long izRequest-URI Too Longz-The request URI was too long for this server.N)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdS)HTTPUnsupportedMediaTypea subclass of :class:`~HTTPClientError` This indicates that the server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. code: 415, title: Unsupported Media Type izUnsupported Media TypeN)r/r0r1rLrrrrrrrs rc@seZdZdZdZdZdZdS)HTTPRequestRangeNotSatisfiablea subclass of :class:`~HTTPClientError` The server SHOULD return a response with this status code if a request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. code: 416, title: Request Range Not Satisfiable izRequest Range Not Satisfiablez%The Range requested is not available.N)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdZdS)HTTPExpectationFailedz subclass of :class:`~HTTPClientError` This indicates that the expectation given in an Expect request-header field could not be met by this server. code: 417, title: Expectation Failed izExpectation FailedzExpectation failed.N)r/r0r1rLrrr$rrrrr src@seZdZdZdZdZdZdS)HTTPUnprocessableEntitya] subclass of :class:`~HTTPClientError` This indicates that the server is unable to process the contained instructions. May be used to notify the client that their JSON/XML is well formed, but not correct for the current request. See RFC4918 section 11 for more information. code: 422, title: Unprocessable Entity izUnprocessable Entityz,Unable to process the contained instructionsN)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdZdS) HTTPLockedz~ subclass of :class:`~HTTPClientError` This indicates that the resource is locked. code: 423, title: Locked iLockedzThe resource is lockedN)r/r0r1rLrrr$rrrrr-src@seZdZdZdZdZdZdS)HTTPFailedDependencyz subclass of :class:`~HTTPClientError` This indicates that the method could not be performed because the requested action depended on another action and that action failed. code: 424, title: Failed Dependency izFailed DependencyzsThe method could not be performed because the requested action dependended on another action and that action failedN)r/r0r1rLrrr$rrrrr<src@seZdZdZdZdZdZdS)HTTPPreconditionRequireda0 subclass of :class:`~HTTPClientError` This indicates that the origin server requires the request to be conditional. Its typical use is to avoid the "lost update" problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict. By requiring requests to be conditional, the server can assure that clients are working with the correct copies. RFC 6585.3 code: 428, title: Precondition Required izPrecondition Requiredz9The origin server requires the request to be conditional.N)r/r0r1rLrrr$rrrrrOsrc@seZdZdZdZdZdZdS)HTTPTooManyRequestsz subclass of :class:`~HTTPClientError` This indicates that the user has sent too many requests in a given amount of time ("rate limiting"). RFC 6585.4 code: 429, title: Too Many Requests izToo Many RequestszUThe action could not be performed because there were too many requests by the client.N)r/r0r1rLrrr$rrrrrfs rc@seZdZdZdZdZdZdS)HTTPRequestHeaderFieldsTooLargeaE subclass of :class:`~HTTPClientError` This indicates that the server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields. RFC 6585.5 code: 431, title: Request Header Fields Too Large izRequest Header Fields Too Largez*The requests header fields were too large.N)r/r0r1rLrrr$rrrrrzs rc@seZdZdZdZdZdS)HTTPServerErrorz base class for the 500s, where the server is in-error This is an error condition in which the server is presumed to be in-error. Unless specialized, this is a '500 Internal Server Error'. izInternal Server ErrorN)r/r0r1rLrrrrrrrsrc@seZdZdZdZdS)HTTPInternalServerErrorz subclass of :class:`~HTTPServerError` This indicates that the server encountered an unexpected condition which prevented it from fulfilling the request. code: 500, title: Internal Server Error zRThe server has either erred or is incapable of performing the requested operation.N)r/r0r1rLr$rrrrrsrc@seZdZdZdZdZdS)HTTPNotImplementedz subclass of :class:`~HTTPServerError` This indicates that the server does not support the functionality required to fulfill the request. code: 501, title: Not Implemented izNot ImplementedN)r/r0r1rLrrrrrrrsrc@seZdZdZdZdZdZdS)HTTPBadGatewaya  subclass of :class:`~HTTPServerError` This indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. code: 502, title: Bad Gateway iz Bad Gatewayz Bad gateway.N)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdZdS)HTTPServiceUnavailablez subclass of :class:`~HTTPServerError` This indicates that the server is currently unable to handle the request due to a temporary overloading or maintenance of the server. code: 503, title: Service Unavailable izService UnavailablezFThe server is currently unavailable. Please try again at a later time.N)r/r0r1rLrrr$rrrrrsrc@seZdZdZdZdZdZdS)HTTPGatewayTimeoutaw subclass of :class:`~HTTPServerError` This indicates that the server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request. code: 504, title: Gateway Timeout izGateway TimeoutzThe gateway has timed out.N)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdZdS)HTTPVersionNotSupportedz subclass of :class:`~HTTPServerError` This indicates that the server does not support, or refuses to support, the HTTP protocol version that was used in the request message. code: 505, title: HTTP Version Not Supported izHTTP Version Not Supportedz"The HTTP version is not supported.N)r/r0r1rLrrr$rrrrrs rc@seZdZdZdZdZdZdS)HTTPInsufficientStoragez subclass of :class:`~HTTPServerError` This indicates that the server does not have enough space to save the resource. code: 507, title: Insufficient Storage izInsufficient Storagez/There was not enough space to save the resourceN)r/r0r1rLrrr$rrrrrsrcKst|f|}|S)zCreates an HTTP exception based on a status code. Example:: raise exception_response(404) # raises an HTTPNotFound exception. The values passed as ``kw`` are provided to the exception's constructor. ) status_map) status_coder#excrrrexception_responsesrcCst|ts|jp|}|S)N)r rrJ)contextrequestrrrdefault_exceptionresponse_view"s  r_r)WrLr,stringrZwebobrr7Zwebob.acceptparserZzope.interfacerZpyramid.interfacesrZpyramid.responserZ pyramid.utilrrrrZWSGIHTTPExceptionrKrMrNrOrRrUrXrZr\r^r`rfrgrhrjrkrlrmrnrorprqrsrtrwrxryrzr{r|r~rrrrrrrrrrrrrrrrrrrrrrrrrlistglobalsr;namer r type issubclassr<getattrrrrrs         B    5 A