Ñò
ô†³Kc 4 @ s d Z d d k Z d d k Z d d k Z d d k l Z l Z l Z d d k l Z d d k
l Z d d d d d
g Z d
e
f d „ ƒ YZ e d ƒ Z e d
ƒ Z e d ƒ Z e d ƒ Z e d ƒ Z e d ƒ Z x> e ƒ i ƒ D]- \ Z Z e e e ƒ o e i e ƒ n qé Wh Z d e f d „ ƒ YZ d e f d „ ƒ YZ d e f d „ ƒ YZ d e f d „ ƒ YZ e! d „ Z" e# e# e# e# d „ Z$ e! d „ Z% d e f d „ ƒ YZ& d e f d „ ƒ YZ' e' d d! d" ƒ d# e f d$ „ ƒ YZ( e( d% d& d' ƒ d( e f d) „ ƒ YZ) e) d* d& d+ ƒ d, e f d- „ ƒ YZ* e* d. d& d/ ƒ d0 e& f d1 „ ƒ YZ+ e+ d2 d3 d4 ƒ d5 e f d6 „ ƒ YZ, e, d7 d3 d8 ƒ d9 e f d: „ ƒ YZ- e- d; d3 d< ƒ d= e f d> „ ƒ YZ. e. d? d@ dA ƒ dB e f dC „ ƒ YZ/ e/ dD d& dE ƒ dF e f dG „ ƒ YZ0 e0 dH d3 dI ƒ x.dJ d3 dK dL dM f dN d3 dK dL dO f dP d3 dK dL dQ f dR d@ dK dS dE f dT d& dU dL dV f dW d3 dU dL dX f dY d! dK dL dZ f d[ d& dU dL d\ f d] d& dK dL d^ f d_ d& dK dS d` f da d& dK dS db f dc d! dU dd de f df d@ dK dS dg f dh d3 dK dL di f dj d& dU dd dk f dl d3 dU dS dm f dn d3 dK dS do f dp d3 dK dL dq f dr d3 dK dL ds f dt d3 dK dS du f dv d3 dK dd dw f dx d& dU dd dy f dz d@ dU dS d{ f d| d3 dK dS d} f d~ d! dU dL d f d€ d@ dK dL d f d‚ d3 dK dS dƒ f d„ d3 dU dS d… f d† d@ dK dS d‡ f dˆ d@ dU dS d‰ f dŠ d@ dU d‹ dX f dŒ d3 dK dL d f dŽ d! dK dL d f d d! dK dL d‘ f d’ d! dK dL d“ f d” d3 dU dS d• f d– d@ dK dL d— f d˜ d! dK dL d™ f dš d! dK d‹ d› f dœ d@ dU d‹ d f f( D]V \ Z1 Z2 Z3 Z4 Z5 h e dL 6e d‹ 6e& dd 6e dS 6e4 Z6 e5 e6 e1 e2 e5 e3 ƒ _ [6 qWxI e i7 ƒ D]; Z8 e8 i1 i9 dž dŸ ƒ i: ƒ Z; e8 e< ƒ e; ƒ o
e? e e ƒ o e= i e ƒ n qËWd S( sÁ
HTTP Message Header Fields (see RFC 4229)
This contains general support for HTTP/1.1 message headers [1]_ in a
manner that supports WSGI ``environ`` [2]_ and ``response_headers``
[3]_. Specifically, this module defines a ``HTTPHeader`` class whose
instances correspond to field-name items. The actual field-content for
the message-header is stored in the appropriate WSGI collection (either
the ``environ`` for requests, or ``response_headers`` for responses).
Each ``HTTPHeader`` instance is a callable (defining ``__call__``)
that takes one of the following:
- an ``environ`` dictionary, returning the corresponding header
value by according to the WSGI's ``HTTP_`` prefix mechanism, e.g.,
``USER_AGENT(environ)`` returns ``environ.get('HTTP_USER_AGENT')``
- a ``response_headers`` list, giving a comma-delimited string for
each corresponding ``header_value`` tuple entries (see below).
- a sequence of string ``*args`` that are comma-delimited into
a single string value: ``CONTENT_TYPE("text/html","text/plain")``
returns ``"text/html, text/plain"``
- a set of ``**kwargs`` keyword arguments that are used to create
a header value, in a manner dependent upon the particular header in
question (to make value construction easier and error-free):
``CONTENT_DISPOSITION(max_age=CONTENT_DISPOSITION.ONEWEEK)``
returns ``"public, max-age=60480"``
Each ``HTTPHeader`` instance also provides several methods to act on
a WSGI collection, for removing and setting header values.
``delete(collection)``
This method removes all entries of the corresponding header from
the given collection (``environ`` or ``response_headers``), e.g.,
``USER_AGENT.remove(environ)`` deletes the 'HTTP_USER_AGENT' entry
from the ``environ``.
``update(collection, *args, **kwargs)``
This method does an in-place replacement of the given header entry,
for example: ``CONTENT_LENGTH(response_headers,len(body))``
The first argument is a valid ``environ`` dictionary or
``response_headers`` list; remaining arguments are passed on to
``__call__(*args, **kwargs)`` for value construction.
``apply(collection, **kwargs)``
This method is similar to update, only that it may affect other
headers. For example, according to recommendations in RFC 2616,
certain Cache-Control configurations should also set the
``Expires`` header for HTTP/1.0 clients. By default, ``apply()``
is simply ``update()`` but limited to keyword arguments.
This particular approach to managing headers within a WSGI collection
has several advantages:
1. Typos in the header name are easily detected since they become a
``NameError`` when executed. The approach of using header strings
directly can be problematic; for example, the following should
return ``None`` : ``environ.get("HTTP_ACCEPT_LANGUAGES")``
2. For specific headers with validation, using ``__call__`` will
result in an automatic header value check. For example, the
_ContentDisposition header will reject a value having ``maxage``
or ``max_age`` (the appropriate parameter is ``max-age`` ).
3. When appending/replacing headers, the field-name has the suggested
RFC capitalization (e.g. ``Content-Type`` or ``ETag``) for
user-agents that incorrectly use case-sensitive matches.
4. Some headers (such as ``Content-Type``) are 0, that is,
only one entry of this type may occur in a given set of
``response_headers``. This module knows about those cases and
enforces this cardinality constraint.
5. The exact details of WSGI header management are abstracted so
the programmer need not worry about operational differences
between ``environ`` dictionary or ``response_headers`` list.
6. Sorting of ``HTTPHeaders`` is done following the RFC suggestion
that general-headers come first, followed by request and response
headers, and finishing with entity-headers.
7. Special care is given to exceptional cases such as Set-Cookie
which violates the RFC's recommendation about combining header
content into a single entry using comma separation.
A particular difficulty with HTTP message headers is a categorization
of sorts as described in section 4.2:
Multiple message-header fields with the same field-name MAY be
present in a message if and only if the entire field-value for
that header field is defined as a comma-separated list [i.e.,
#(values)]. It MUST be possible to combine the multiple header
fields into one "field-name: field-value" pair, without changing
the semantics of the message, by appending each subsequent
field-value to the first, each separated by a comma.
This creates three fundamentally different kinds of headers:
- Those that do not have a #(values) production, and hence are
singular and may only occur once in a set of response fields;
this case is handled by the ``_SingleValueHeader`` subclass.
- Those which have the #(values) production and follow the
combining rule outlined above; our ``_MultiValueHeader`` case.
- Those which are multi-valued, but cannot be combined (such as the
``Set-Cookie`` header due to its ``Expires`` parameter); or where
combining them into a single header entry would cause common
user-agents to fail (``WWW-Authenticate``, ``Warning``) since
they fail to handle dates even when properly quoted. This case
is handled by ``_MultiEntryHeader``.
Since this project does not have time to provide rigorous support
and validation for all headers, it does a basic construction of
headers listed in RFC 2616 (plus a few others) so that they can
be obtained by simply doing ``from paste.httpheaders import *``;
the name of the header instance is the "common name" less any
dashes to give CamelCase style names.
.. [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
.. [2] http://www.python.org/peps/pep-0333.html#environ-variables
.. [3] http://www.python.org/peps/pep-0333.html#the-start-response-callable
iÿÿÿÿN( t
formatdatet parsedate_tzt mktime_tz( t time( t HTTPBadRequestt
get_headert list_headerst normalize_headerst
HTTPHeadert EnvironVariablec B s) e Z d Z d „ Z d „ Z d „ Z RS( sµ
a CGI ``environ`` variable as described by WSGI
This is a helper object so that standard WSGI ``environ`` variables
can be extracted w/o syntax error possibility.
c C s | i | d ƒ S( Nt ( t get( t selft environ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt __call__š s c C s d | S( Ns ( ( R ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt __repr__œ s c C s | | | ( R2 t __class__R R/ ( R t ref( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR l s c O sö | p | i | St t | d ƒ j ot g } | i i ƒ } xW g } | d D]* \ } } | i ƒ | j o | | qS qS ~ D] } | i | ƒ q„ W| St t | d ƒ j o* | d i | i ƒ } | p d S| f Sx | D] } qè W| S( sq
find/construct field-value(s) for the given header
Resolution is done according to the following arguments:
- If only keyword arguments are given, then this is equivalent
to ``compose(**kwargs)``.
- If the first (and only) argument is a dict, it is assumed
to be a WSGI ``environ`` and the result of the corresponding
``HTTP_`` entry is returned.
- If the first (and only) argument is a list, it is assumed
to be a WSGI ``response_headers`` and the field-value(s)
for this header are collected and returned.
- In all other cases, the arguments are collected, checked that
they are string values, possibly verified by the header's
logic, and returned.
At this time it is an error to provide keyword arguments if args
is present (this might change). It is an error to provide both
a WSGI object and also string arguments. If no arguments are
provided, then ``compose()`` is called to provide a default
value for the header; if there is not default it is an error.
i ( ( R t listt typeR/ R4 t appendt dictR R' ( R R R t resultR/ t _[1]t headerR t item( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt valuesp s& % c O s2 | i | | Ž } | p d St | d ƒ i ƒ S( sÕ
converts ``values()`` into a string value
This method converts the results of ``values()`` into a string
value for common usage. By default, it is asserted that only
one value exists; if you need to access all values then either
call ``values()`` directly, or inherit ``_MultiValueHeader``
which overrides this method to return a comma separated list of
values as described by section 4.2 of RFC 2616.
R
i ( RH t strt strip( R R R RH ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR Ÿ s c C s‘ t | ƒ t j o# | i | j o | | i =n | Sd } xN | t | ƒ j o: | | d i ƒ | i j o | | =q? n | d 7} q? Wd S( sS
removes all occurances of the header from the collection provided
i i N( RA RC R' t lenR4 R+ ( R R! t i( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt delete± s c O sö | i | | Ž } | p | i | ƒ d St | ƒ t j o | | | i Ê s N( R RS RZ RJ R4 t floatRB Rk ( R R R RF RE RX t langst qst langt piecest paramsR® t paramt lvaluet rvaluet _[2]( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR ± s,
5 !
( R R R R ( ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR ¬ s s Accept-Languages RFC 2616, 14.4t
_AcceptRangesc B s e Z d Z d d d „ Z RS( s.
Accept-Ranges, RFC 2616 section 14.5
c C s | o d Sd S( Nt bytest none( s bytes( s none( ( R R¼ R» ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR Ò s N( R R R RS R ( ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyRº Î s s
Accept-RangesR% s RFC 2616, 14.5t
_ContentRangec B s e Z d Z d d d d „ Z RS( s.
Content-Range, RFC 2616 section 14.6
c C s d | | | f } | f S( Ns bytes %d-%d/%d( ( R t
first_bytet last_bytet total_lengthR^ ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR Ü s N( R R R RS R ( ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR½ Ø s s
Content-Ranges RFC 2616, 14.6t _Authorizationc B s, e Z d Z d d d d d d d d „ Z RS( s2
Authorization, RFC 2617 (RFC 2616, 14.8)
c s | p | o4 d | i ƒ | i ƒ f } d | i d ƒ i ƒ Sˆ p d ‰ | i d ƒ \ } }
|
i d d ƒ \ }
} t i ƒ } | i |
ˆ | | ƒ | i d d ƒ \ } } t i t i | ƒ ƒ }
d t f ‡ ‡ f d
† ƒ Y} d | i | ƒ |
ƒ } | f S( Ns %s:%ss Basic %st base64Rœ s realm="t "i t t FakeRequestc s5 e Z ‡ f d † Z d „ Z ‡ f d † Z e Z RS( c s ˆ S( N( ( R ( t path( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt get_full_url÷ s c S s t S( N( R, ( R ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt has_dataù s c s ˆ p d S( Nt GET( ( R ( t method( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt
get_methodû s ( R R RÇ RÈ RË t get_selector( ( RÆ RÊ ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyRÅ ö s s Digest %s(
RJ t encodeRZ t urllib2t AbstractDigestAuthHandlert add_passwordt parse_keqv_listt parse_http_listR- t get_authorization( R t digestt basict usernamet passwordt challengeRÆ RÊ t userpassR* t realmt autht tokent chalRÅ R^ ( ( RÊ RÆ s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyR ç s
N( R R R RS R ( ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyRÁ ã s t
Authorizations RFC 2617t Accepts 1.1s multi-values RFC 2616, 14.1s Accept-Charsets RFC 2616, 14.2s Accept-Encodings RFC 2616, 14.3t Aget singulart Allows 1.0s RFC 2616, 14.7t Cookies RFC 2109/Netscapet
Connections RFC 2616, 14.10s Content-Encodings RFC 2616, 14.11s Content-Languages RFC 2616, 14.12s Content-Locations RFC 2616, 14.14s Content-MD5s RFC 2616, 14.15t Dates date-headers RFC 2616, 14.18t ETags RFC 2616, 14.19t Expects RFC 2616, 14.20t Expiress RFC 2616, 14.21t Froms RFC 2616, 14.22t Hosts RFC 2616, 14.23s If-Matchs RFC 2616, 14.24s
If-None-Matchs RFC 2616, 14.26s If-Ranges RFC 2616, 14.27s If-Unmodified-Sinces RFC 2616, 14.28s
Last-Modifieds RFC 2616, 14.29t Locations RFC 2616, 14.30s Max-Forwardss RFC 2616, 14.31t Pragmas RFC 2616, 14.32s Proxy-Authenticates RFC 2616, 14.33s Proxy-Authorizations RFC 2616, 14.34t Referers RFC 2616, 14.36s Retry-Afters RFC 2616, 14.37t Servers RFC 2616, 14.38s
Set-Cookies multi-entryt TEs RFC 2616, 14.39t Trailers RFC 2616, 14.40s Transfer-Encodings RFC 2616, 14.41t Upgrades RFC 2616, 14.42s
User-Agents RFC 2616, 14.43t Varys RFC 2616, 14.44t Vias RFC 2616, 14.45t Warnings RFC 2616, 14.46s WWW-Authenticates RFC 2616, 14.47R) R* (@ R RŸ RÎ t ret rfc822R R R R Rt t httpexceptionsR t __all__RI R R R R R R R t globalsRz t _namet _objR; RB R3 R- R RT RU R[ RO R RS R R Rs Rw R‰ R— R™ R¡ R£ R Rº R½ RÁ R/ R0 R1 t stylet commentt klassRH Rb R8 R7 t headnamet localst
__pudge_all__RA t
issubclass( ( ( s5 /usr/lib/python2.6/site-packages/paste/httpheaders.pyt ˆ sÖ
ÿ ;
&{ B0