| Server IP : 182.53.201.61 / Your IP : 216.73.217.175 Web Server : Apache/2.2.15 (Fedora) System : Linux km10.dyndns.org 2.6.31.5-127.fc12.i686.PAE #1 SMP Sat Nov 7 21:25:57 EST 2009 i686 User : apache ( 48) PHP Version : 5.3.3 Disable Function : NONE MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/lib/python2.6/site-packages/mod_python/ |
Upload File : |
Ñò µ[PEc @ só d Z d d k Z d d k Z d d k Z d d k Z d d k Z d e f d „ ƒ YZ d e f d „ ƒ YZ d e f d „ ƒ YZ d e f d „ ƒ YZ d e f d „ ƒ YZ e i d ƒ Z d d „ Z d d „ Z e d „ Z e d „ Z d S( s™ This module contains classes to support HTTP State Management Mechanism, also known as Cookies. The classes provide simple ways for creating, parsing and digitally signing cookies, as well as the ability to store simple Python objects in Cookies (using marshalling). The behaviour of the classes is designed to be most useful within mod_python applications. The current state of HTTP State Management standardization is rather unclear. It appears that the de-facto standard is the original Netscape specification, even though already two RFC's have been put out (RFC2109 (1997) and RFC2965 (2000)). The RFC's add a couple of useful features (e.g. using Max-Age instead of Expires, but my limited tests show that Max-Age is ignored by the two browsers tested (IE and Safari). As a result of this, perhaps trying to be RFC-compliant (by automatically providing Max-Age and Version) could be a waste of cookie space... iÿÿÿÿNt CookieErrorc B s e Z RS( ( t __name__t __module__( ( ( s5 /usr/lib/python2.6/site-packages/mod_python/Cookie.pyR 4 s t metaCookiec B s e Z d „ Z RS( c C se d } | d } | | d <| | d <d „ } d „ } t d | d | ƒ | d <t i | | | | ƒ S( Nt versiont patht domaint securet commentt expirest max_aget commentURLt discardt portt httponlyt namet valuet _valuet _expirest __data__t _valid_attrt __slots__c S s— t | ƒ t d ƒ j oL y t i | d ƒ } Wn t j o t d | ‚ n Xt i | ƒ } n"