Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4
XMc@ssdZddddddddgZd d d d d ddddddddddgZd d d d dd dddddddddddddddddgZd d d!d"ddd dd#d$g Zd d dd d ddddd#d$dddgZd dd dddd ddd#d$dg Zd d d d d"d dddddddg Zd%Zd&Z hZ d'Z d(e fd)YZ d*d+klZd,ed,d-e fd.YZd/ed/d0e fd1YZded2Zd3Zd4d5Zded6Zd7Zd8Zed9Zd:Zd;Zed<eDZd=Zd4d4d>Zd4d4d?Z d@S(AsParse (absolute and relative) URLs. urlparse module is based upon the following RFC specifications. RFC 3986 (STD66): "Uniform Resource Identifiers" by T. Berners-Lee, R. Fielding and L. Masinter, January 2005. RFC 2396: "Uniform Resource Identifiers (URI)": Generic Syntax by T. Berners-Lee, R. Fielding, and L. Masinter, August 1998. RFC 2368: "The mailto URL scheme", by P.Hoffman , L Masinter, J. Zwinski, July 1998. RFC 1808: "Relative Uniform Resource Locators", by R. Fielding, UC Irvine, June 1995. RFC 1738: "Uniform Resource Locators (URL)" by T. Berners-Lee, L. Masinter, M. McCahill, December 1994 RFC 3986 is considered the current standard and any future changes to urlparse module should conform with it. The urlparse module is currently not entirely compliant with this RFC due to defacto scenarios for parsing, and for backward compatibility purposes, some parsing quirks from older RFCs are retained. The testcases in test_urlparse.py provides a good indicator of parsing behavior. turlparset urlunparseturljoint urldefragturlsplitt urlunsplittparse_qst parse_qsltftpthttptgophertnntptimaptwaistfilethttpstshttptmmstprosperotrtsptrtsputtsftpttelnettsnewstrsynctsvnssvn+sshtnfstgitsgit+sshthdltmailtotnewstsiptsipssAabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789+-.icCstidS(sClear the parse cache.N(t _parse_cachetclear(((s/usr/lib/python2.6/urlparse.pyt clear_cache;st ResultMixincBsJeZdZedZedZedZedZRS(s-Shared methods for the parsed result objects.cCs\|i}d|joB|iddd}d|jo|iddd}n|SdS(Nt@iit:(tnetloctrsplittsplittNone(tselfR(tuserinfo((s/usr/lib/python2.6/urlparse.pytusernameCs   cCsV|i}d|jo<|iddd}d|jo|idddSndS(NR&iiR'(R(R)R*R+(R,R(R-((s/usr/lib/python2.6/urlparse.pytpasswordMs    cCsh|i}d|jo|iddd}nd|jo|iddd}n|ipdS(NR&iR'i(R(R)R*tlowerR+(R,R(((s/usr/lib/python2.6/urlparse.pythostnameVs    cCse|i}d|jo|iddd}nd|jo$|iddd}t|dSdS(NR&iR'i (R(R)R*tintR+(R,R(tport((s/usr/lib/python2.6/urlparse.pyR3_s   (t__name__t __module__t__doc__tpropertyR.R/R1R3(((s/usr/lib/python2.6/urlparse.pyR%@s    i(t namedtuplet SplitResults!scheme netloc path query fragmentcBseZdZdZRS(cCs t|S(N(R(R,((s/usr/lib/python2.6/urlparse.pytgeturlos((R4R5t __slots__R:(((s/usr/lib/python2.6/urlparse.pyR9kst ParseResults(scheme netloc path params query fragmentcBseZdZdZRS(cCs t|S(N(R(R,((s/usr/lib/python2.6/urlparse.pyR:ws((R4R5R;R:(((s/usr/lib/python2.6/urlparse.pyR<sscCsvt|||}|\}}}}}|tjo#d|jot|\}}nd}t||||||S(s#Parse a URL into 6 components: :///;?# Return a 6-tuple: (scheme, netloc, path, params, query, fragment). Note that we don't break the components up in smaller bits (e.g. netloc is a single string) and we don't expand % escapes.t;R(Rt uses_paramst _splitparamsR<(turltschemetallow_fragmentsttupleR(tquerytfragmenttparams((s/usr/lib/python2.6/urlparse.pyR{s cCsid|jo7|id|id}|djo |dfSn|id}|| ||dfS(Nt/R=iRi(tfindtrfind(R@ti((s/usr/lib/python2.6/urlparse.pyR?s   icCsdt|}x@dD]8}|i||}|djot||}qqW|||!||fS(Ns/?#i(tlenRHtmin(R@tstarttdelimtctwdelim((s/usr/lib/python2.6/urlparse.pyt _splitnetlocs  c Csyt|}|||t|t|f}ti|d }|o|Stttjo tnd}}}|id}|djo#|| djo|| i }||d}|d djot |d\}}n|o)d|jo|i dd\}}nd |jo|i d d\}}nt |||||} | t|<| SxG|| D]} | t joPqwqwW|| i ||d}}n|d djot |d\}}n|o6|tjo)d|jo|i dd\}}n|tjo)d |jo|i d d\}}nt |||||} | t|<| S( sParse a URL into 5 components: :///?# Return a 5-tuple: (scheme, netloc, path, query, fragment). Note that we don't break the components up in smaller bits (e.g. netloc is a single string) and we don't expand % escapes.RR'iR iis//t#t?N(tboolttypeR"tgetR+RKtMAX_CACHE_SIZER$RHR0RQR*R9t scheme_charst uses_fragmentt uses_query( R@RARBtkeytcachedR(RDRERJtvRO((s/usr/lib/python2.6/urlparse.pyRsH !       #! cCsL|\}}}}}}|od||f}nt|||||fS(sPut a parsed URL back together again. This may result in a slightly different, but equivalent URL, if the URL that was parsed originally had redundant delimiters, e.g. a ? with an empty query (the draft states that these are equivalent).s%s;%s(R(tdataRAR(R@RFRDRE((s/usr/lib/python2.6/urlparse.pyRscCs|\}}}}}|p%|o]|tjoP|d djo?|o|d djod|}nd|pd|}n|o|d|}n|o|d|}n|o|d|}n|S( skCombine the elements of a tuple as returned by urlsplit() into a complete URL as a string. The data argument can be any five-item iterable. This may result in a slightly different, but equivalent URL, if the URL that was parsed originally had unnecessary delimiters (for example, a ? with an empty query; the RFC states that these are equivalent).is//iRGRR'RSRR(t uses_netloc(R^RAR(R@RDRE((s/usr/lib/python2.6/urlparse.pyRs,c Cs|p|S|p|St|d|\}}}}}}t|||\} } } } } }| |jp | tjo|S| tjo.| ot| | | | | |fS|} n| d djot| | | | | |fS| pk|} | p |} n'| d } t| | | | | |fS| p |} nt| | | | | |fS|idd | id}|ddjod|d/s c Cs|id}xtdt|D]}||}yt|d |d|| 'abc def'.t%iiiR( R*txrangeRKt _hextochrtKeyErrortUnicodeDecodeErrortunichrR2Rc(RntresRJtitem((s/usr/lib/python2.6/urlparse.pytunquote1s .cCs\h}xOt|||D];\}}||jo||i|q|g||s  c Cs8g}|idD]#}|idD] }||q'q~}g}x|D]}| o| oqMn|idd} t| djo:|otd|fn|o| idqqMnt| dp|oOt| did d } t| did d } |i| | fqMqMW|S( sParse a query given as a string argument. Arguments: qs: URL-encoded query string to be parsed keep_blank_values: flag indicating whether blank values in URL encoded queries should be treated as blank strings. A true value indicates that blanks should be retained as blank strings. The default false value indicates that blank values are to be ignored and treated as if they were not included. strict_parsing: flag indicating what to do with parsing errors. If false (the default), errors are silently ignored. If true, errors raise a ValueError exception. Returns a list, as G-d intended. t&R=t=iisbad query field: %rRit+t (R*RKt ValueErrorRRtreplace( RRRt_[1]ts1ts2tpairstrt name_valuetnvRR((s/usr/lib/python2.6/urlparse.pyRXs$@N(!R6t__all__RaR_tnon_hierarchicalR>RZRYRXRWR"R$tobjectR%t collectionsR8R9R<tTrueRR?RQRRRRRRuRR{RRR(((s/usr/lib/python2.6/urlparse.pytsP   )"" ,  9