Current File : //opt/rh/rh-python35/root/lib64/python3.5/http/__pycache__/server.cpython-35.pyc
���\�� � @ sb d Z d Z d d d d g Z d d l Z d d l Z d d l Z d d l Z d d l Z d d l Z d d l
Z
d d l Z d d l Z d d l
Z
d d l Z d d l Z d d l Z d d l Z d d l Z d d l m Z d Z d
Z d d � Z Gd
d � d e
j � Z Gd d � d e
j � Z Gd d � d e � Z d d � Z d a d d � Z d d � Z Gd d � d e � Z! e e d d d d d � Z" e# d k r^e j$ � Z% e% j& d d d d d! �e% j& d" d# d$ d d% d& d d' �e% j& d( d d) d$ d d* e' d+ d, d d- �e% j( � Z) e) j* r9e! Z+ n e Z+ e" d. e+ d( e) j, d/ e) j- � d S)0a@ HTTP server classes.
Note: BaseHTTPRequestHandler doesn't implement any HTTP request; see
SimpleHTTPRequestHandler for simple implementations of GET, HEAD and POST,
and CGIHTTPRequestHandler for CGI scripts.
It does, however, optionally implement HTTP/1.1 persistent connections,
as of version 0.3.
Notes on CGIHTTPRequestHandler
------------------------------
This class implements GET and POST requests to cgi-bin scripts.
If the os.fork() function is not present (e.g. on Windows),
subprocess.Popen() is used as a fallback, with slightly altered semantics.
In all cases, the implementation is intentionally naive -- all
requests are executed synchronously.
SECURITY WARNING: DON'T USE THIS CODE UNLESS YOU ARE INSIDE A FIREWALL
-- it may execute arbitrary Python code or external programs.
Note that status code 200 is sent prior to execution of a CGI script, so
scripts cannot send other status codes such as 302 (redirect).
XXX To do:
- log requests even later (to capture byte count)
- log user-agent header and other interesting goodies
- send error log to separate file
z0.6�
HTTPServer�BaseHTTPRequestHandler�SimpleHTTPRequestHandler�CGIHTTPRequestHandler� N)�
HTTPStatusa� <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<title>Error response</title>
</head>
<body>
<h1>Error response</h1>
<p>Error code: %(code)d</p>
<p>Message: %(message)s.</p>
<p>Error code explanation: %(code)s - %(explain)s.</p>
</body>
</html>
ztext/html;charset=utf-8c C s( | j d d � j d d � j d d � S)N�&z&�<z<�>z>)�replace)�html� r �;/opt/rh/rh-python35/root/usr/lib64/python3.5/http/server.py� _quote_html� s r c @ s" e Z d Z d Z d d � Z d S)r � c C sN t j j | � | j j � d d � \ } } t j | � | _ | | _ d S)z.Override server_bind to store the server name.N� )� socketserver� TCPServer� server_bind�socket� getsocknameZgetfqdn� server_name� server_port)�self�host�portr r r
r � s zHTTPServer.server_bindN)�__name__�
__module__� __qualname__Zallow_reuse_addressr r r r r
r � s c
@ s� e Z d Z d Z d e j j � d Z d e Z e
Z e Z
d Z d d � Z d d � Z d
d � Z d d
� Z d d d d � Z d d d � Z d d d � Z d d � Z d d � Z d d � Z d d d d � Z d d � Z d d! � Z d" d# � Z d d$ d% � Z d& d' � Z d( d) d* d+ d, d- d. g Z d d/ d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 d: g
Z d; d< � Z! d= Z" e# j$ j% Z& d> d? � e' j( j) � D� Z* d S)@r a� HTTP request handler base class.
The following explanation of HTTP serves to guide you through the
code as well as to expose any misunderstandings I may have about
HTTP (so you don't need to read the code to figure out I'm wrong
:-).
HTTP (HyperText Transfer Protocol) is an extensible protocol on
top of a reliable stream transport (e.g. TCP/IP). The protocol
recognizes three parts to a request:
1. One line identifying the request type and path
2. An optional set of RFC-822-style headers
3. An optional data part
The headers and data are separated by a blank line.
The first line of the request has the form
<command> <path> <version>
where <command> is a (case-sensitive) keyword such as GET or POST,
<path> is a string containing path information for the request,
and <version> should be the string "HTTP/1.0" or "HTTP/1.1".
<path> is encoded using the URL encoding scheme (using %xx to signify
the ASCII character with hex code xx).
The specification specifies that lines are separated by CRLF but
for compatibility with the widest range of clients recommends
servers also handle LF. Similarly, whitespace in the request line
is treated sensibly (allowing multiple spaces between components
and allowing trailing whitespace).
Similarly, for output, lines ought to be separated by CRLF pairs
but most clients grok LF characters just fine.
If the first line of the request has the form
<command> <path>
(i.e. <version> is left out) then this is assumed to be an HTTP
0.9 request; this form has no optional headers and data part and
the reply consists of just the data.
The reply form of the HTTP 1.x protocol again has three parts:
1. One line giving the response code
2. An optional set of RFC-822-style headers
3. The data
Again, the headers and data are separated by a blank line.
The response code line has the form
<version> <responsecode> <responsestring>
where <version> is the protocol version ("HTTP/1.0" or "HTTP/1.1"),
<responsecode> is a 3-digit response code indicating success or
failure of the request, and <responsestring> is an optional
human-readable string explaining what the response code means.
This server parses the request and the headers, and then calls a
function specific to the request type (<command>). Specifically,
a request SPAM will be handled by a method do_SPAM(). If no
such method exists the server sends an error response to the
client. If it exists, it is called with no arguments:
do_SPAM()
Note that the request name is case sensitive (i.e. SPAM and spam
are different requests).
The various request details are stored in instance variables:
- client_address is the client IP address in the form (host,
port);
- command, path and version are the broken-down request line;
- headers is an instance of email.message.Message (or a derived
class) containing the header information;
- rfile is a file object open for reading positioned at the
start of the optional input data part;
- wfile is a file object open for writing.
IT IS IMPORTANT TO ADHERE TO THE PROTOCOL FOR WRITING!
The first thing to be written must be the response line. Then
follow 0 or more header lines, then a blank line, and then the
actual data (if any). The meaning of the header lines depends on
the command executed by the server; in most cases, when data is
returned, there should be at least one header line of the form
Content-type: <type>/<subtype>
where <type> and <subtype> should be registered MIME types,
e.g. "text/html" or "text/plain".
zPython/r z BaseHTTP/zHTTP/0.9c
C s/ d | _ | j | _ } d | _ t | j d � } | j d � } | | _ | j � } t | � d k r�| \ } } } | d d � d k r� | j
t j d | � d Sya | j d
d � d } | j d � } t | � d
k r� t
� t | d � t | d � f } Wn3 t
t f k
r@| j
t j d | � d SYn X| d k re| j d k red | _ | d k r| j
t j d | � d Snv t | � d
k r�| \ } } d | _ | d k r| j
t j d | � d Sn% | s�d S| j
t j d | � d S| | | | _ | _ | _ y% t j j | j d | j �| _ Wn/ t j j k
rx| j
t j d � d SYn X| j j d d � } | j � d k r�d | _ n* | j � d k r�| j d k r�d | _ | j j d d � } | j � d k r+| j d k r+| j d k r+| j � s+d Sd S) a' Parse a request (internal).
The request should be stored in self.raw_requestline; the results
are in self.command, self.path, self.request_version and
self.headers.
Return True for success, False for failure; on failure, an
error is sent back.
NTz
iso-8859-1z
� � zHTTP/zBad request version (%r)F�/r �.r r zHTTP/1.1zInvalid HTTP Version (%s)ZGETz Bad HTTP/0.9 request type (%r)zBad request syntax (%r)Z_classz
Line too long�
Connection� �closez
keep-aliveZExpectz 100-continue)r r )r r ) �command�default_request_version�request_version�close_connection�str�raw_requestline�rstrip� requestline�split�len�
send_errorr Z BAD_REQUEST�
ValueError�int�
IndexError�protocol_versionZHTTP_VERSION_NOT_SUPPORTED�path�http�clientZ
parse_headers�rfile� MessageClass�headersZ LineTooLong�get�lower�handle_expect_100)
r �versionr, �wordsr% r4 Zbase_version_numberZversion_numberZconntypeZexpectr r r
�
parse_request s� $ z$BaseHTTPRequestHandler.parse_requestc C s | j t j � | j � d S)a7 Decide what to do with an "Expect: 100-continue" header.
If the client is expecting a 100 Continue response, we must
respond with either a 100 Continue or a final response before
waiting for the request body. The default is to always respond
with a 100 Continue. You can behave differently (for example,
reject unauthorized requests) by overriding this method.
This method should either return True (possibly after sending
a 100 Continue response) or send an error response and return
False.
T)�send_response_onlyr ZCONTINUE� end_headers)r r r r
r< d s
z(BaseHTTPRequestHandler.handle_expect_100c C s, y� | j j d � | _ t | j � d k r\ d | _ d | _ d | _ | j t j � d S| j sr d | _
d S| j � s� d Sd | j } t | | � s� | j t j
d | j � d St | | � } | � | j j � WnE t j k
r'} z" | j d | � d | _
d SWYd d } ~ Xn Xd S) z�Handle a single HTTP request.
You normally don't need to override this method; see the class
__doc__ string for information on how to handle specific HTTP
commands such as GET and POST.
i i r# NTZdo_zUnsupported method (%r)zRequest timed out: %r)r7 �readliner* r. r, r' r% r/ r ZREQUEST_URI_TOO_LONGr( r? �hasattr�NOT_IMPLEMENTED�getattr�wfile�flushr Ztimeout� log_error)r Zmname�method�er r r
�handle_one_requestv s4
z)BaseHTTPRequestHandler.handle_one_requestc C s1 d | _ | j � x | j s, | j � q Wd S)z&Handle multiple requests if necessary.TN)r( rK )r r r r
�handle� s
z BaseHTTPRequestHandler.handleNc C sL y | j | \ } } Wn t k
r7 d \ } } Yn X| d k rJ | } | d k r\ | } | j d | | � | j d | d t | � d t | � i } | j d d � } | j | | � | j d | j � | j d
d � | j d t t
| � � � | j � | j d
k rH| d k rH| t
j t
j f k rH| j j | � d S)ak Send and log an error reply.
Arguments are
* code: an HTTP error code
3 digits
* message: a simple optional 1 line reason phrase.
*( HTAB / SP / VCHAR / %x80-FF )
defaults to short entry matching the response code
* explain: a detailed message defaults to the long entry
matching the response code.
This sends an error response (so it must be called before any
output has been generated), logs the error, and finally sends
a piece of HTML explaining the error to the user.
�???Nzcode %d, message %s�code�message�explainzUTF-8r
z Content-Typer" r$ zContent-LengthZHEAD�� )rM rM )� responses�KeyErrorrH �error_message_formatr �encode�
send_response� send_header�error_content_typer1 r. rA r% r Z
NO_CONTENTZ NOT_MODIFIEDrF �write)r rN rO rP ZshortmsgZlongmsgZcontentZbodyr r r
r/ � s,
%
z!BaseHTTPRequestHandler.send_errorc C sM | j | � | j | | � | j d | j � � | j d | j � � d S)z�Add the response header to the headers buffer and log the
response code.
Also send two standard headers with the server software
version and the current date.
ZServerZDateN)� log_requestr@ rW �version_string�date_time_string)r rN rO r r r
rV � s
z$BaseHTTPRequestHandler.send_responsec C s� | d k r5 | | j k r/ | j | d } n d } | j d k r� t | d � s\ g | _ | j j d | j | | f j d d � � d S) z Send the response header only.Nr r# zHTTP/0.9�_headers_bufferz
%s %d %s
zlatin-1�strict)rR r' rC r] �appendr3 rU )r rN rO r r r
r@ � s z)BaseHTTPRequestHandler.send_response_onlyc C s� | j d k rM t | d � s' g | _ | j j d | | f j d d � � | j � d k r� | j � d k r} d | _ n | j � d k r� d
| _ d S) z)Send a MIME header to the headers buffer.zHTTP/0.9r] z%s: %s
zlatin-1r^ Z
connectionr$ Tz
keep-aliveFN)r' rC r] r_ rU r; r( )r �keyword�valuer r r
rW � s z"BaseHTTPRequestHandler.send_headerc C s- | j d k r) | j j d � | j � d S)z,Send the blank line ending the MIME headers.zHTTP/0.9s
N)r' r] r_ �
flush_headers)r r r r
rA � s z"BaseHTTPRequestHandler.end_headersc C s8 t | d � r4 | j j d j | j � � g | _ d S)Nr] � )rC rF rY �joinr] )r r r r
rb � s z$BaseHTTPRequestHandler.flush_headers�-c C sA t | t � r | j } | j d | j t | � t | � � d S)zNLog an accepted request.
This is called by send_response().
z
"%s" %s %sN)�
isinstancer ra � log_messager, r) )r rN �sizer r r
rZ s z"BaseHTTPRequestHandler.log_requestc G s | j | | � d S)z�Log an error.
This is called when a request cannot be fulfilled. By
default it passes the message on to log_message().
Arguments are the same as for log_message().
XXX This should go to the separate error log.
N)rg )r �format�argsr r r
rH
s z BaseHTTPRequestHandler.log_errorc G s1 t j j d | j � | j � | | f � d S)a� Log an arbitrary message.
This is used by all other logging functions. Override
it if you have specific logging wishes.
The first argument, FORMAT, is a format string for the
message to be logged. If the format string contains
any % escapes requiring parameters, they should be
specified as subsequent arguments (it's just like
printf!).
The client ip and current date/time are prefixed to
every message.
z%s - - [%s] %s
N)�sys�stderrrY �address_string�log_date_time_string)r ri rj r r r
rg s z"BaseHTTPRequestHandler.log_messagec C s | j d | j S)z*Return the server software version string.� )�server_version� sys_version)r r r r
r[ 1 s z%BaseHTTPRequestHandler.version_stringc C ss | d k r t j � } t j | � \ } } } } } } } } }
d | j | | | j | | | | | f } | S)z@Return the current date and time formatted for a message header.Nz#%s, %02d %3s %4d %02d:%02d:%02d GMT)�timeZgmtime� weekdayname� monthname) r Z timestamp�year�month�day�hh�mm�ssZwd�y�z�sr r r
r\ 5 s *
z'BaseHTTPRequestHandler.date_time_stringc C s] t j � } t j | � \ } } } } } } } } }
d | | j | | | | | f } | S)z.Return the current time formatted for logging.z %02d/%3s/%04d %02d:%02d:%02d)rr Z localtimert ) r Znowru rv rw rx ry rz �xr{ r| r} r r r
rn @ s
* z+BaseHTTPRequestHandler.log_date_time_stringZMonZTueZWedZThuZFriZSatZSunZJanZFebZMarZAprZMayZJunZJulZAugZSepZOctZNovZDecc C s | j d S)zReturn the client address.r )�client_address)r r r r
rm N s z%BaseHTTPRequestHandler.address_stringzHTTP/1.0c C s% i | ] } | j | j f | � q Sr )�phraseZ description)�.0�vr r r
�
<dictcomp>] s z!BaseHTTPRequestHandler.<dictcomp>)+r r r �__doc__rk r= r- rq � __version__rp �DEFAULT_ERROR_MESSAGErT �DEFAULT_ERROR_CONTENT_TYPErX r& r? r< rK rL r/ rV r@ rW rA rb rZ rH rg r[ r\ rn rs rt rm r3 r5 r6 Z HTTPMessager8 r Z __members__�valuesrR r r r r
r � s> f
[ % +
c @ s� e Z d Z d Z d e Z d d � Z d d � Z d d � Z d d
� Z d d � Z
d
d � Z d d � Z e
j s� e
j � e
j j � Z e j d d d d d d d d i � d S)r aW Simple HTTP request handler with GET and HEAD commands.
This serves files from the current directory and any of its
subdirectories. The MIME type for files is determined by
calling the .guess_type() method.
The GET and HEAD requests are identical except that the HEAD
request omits the actual contents of the file.
z SimpleHTTP/c
C s; | j � } | r7 z | j | | j � Wd | j � Xd S)zServe a GET request.N)� send_head�copyfilerF r$ )r �fr r r
�do_GETr s
z SimpleHTTPRequestHandler.do_GETc C s | j � } | r | j � d S)zServe a HEAD request.N)r� r$ )r r� r r r
�do_HEAD{ s z SimpleHTTPRequestHandler.do_HEADc C s� | j | j � } d } t j j | � r
t j j | j � } | j j d � s� | j t j
� | d | d | d d | d | d f } t j j | � } | j d | � | j
� d SxI d D]4 } t j j | | � } t j j | � r� | } Pq� W| j | � S| j | � } y t | d � } Wn) t k
rW| j t j d � d SYn Xy} | j t j � | j d
| � t j | j � � } | j d t | d � � | j d | j | j � � | j
� | SWn | j � � Yn Xd S)a{ Common code for GET and HEAD commands.
This sends the response code and MIME headers.
Return value is either a file object (which has to be copied
to the outputfile by the caller unless the command was HEAD,
and must be closed by the caller under all circumstances), or
None, in which case the caller has nothing further to do.
Nr r r r r � ZLocation�
index.html� index.htm�rbzFile not foundz Content-typezContent-Length� z
Last-Modified)r� r� ) �translate_pathr4 �os�isdir�urllib�parseZurlsplit�endswithrV r ZMOVED_PERMANENTLYZ
urlunsplitrW rA rd �exists�list_directory�
guess_type�open�OSErrorr/ � NOT_FOUND�OK�fstat�filenor) r\ �st_mtimer$ ) r r4 r� �partsZ new_partsZnew_url�indexZctypeZfsr r r
r� � sF
z"SimpleHTTPRequestHandler.send_headc
C s` y t j | � } Wn) t k
r> | j t j d � d SYn X| j d d d � � g } y t j j | j
d d �} Wn$ t k
r� t j j | � } Yn Xt j
| � } t j � } d | } | j d � | j d
� | j d | � | j d | � | j d
| � | j d � x� | D]� } t j
j | | � } | } }
t j
j | � rr| d } | d }
t j
j | � r�| d } | j d t j j |
d d �t j
| � f � q'W| j d � d j | � j | d � } t j � } | j | � | j d � | j t j � | j d d | � | j d t t | � � � | j � | S)z�Helper to produce a directory listing (absent index.html).
Return value is either a file object, or None (indicating an
error). In either case, the headers are sent, making the
interface the same as for send_head().
z No permission to list directoryN�keyc S s
| j � S)N)r; )�ar r r
�<lambda>� s z9SimpleHTTPRequestHandler.list_directory.<locals>.<lambda>�errors�
surrogatepasszDirectory listing for %szZ<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">z
<html>
<head>z@<meta http-equiv="Content-Type" content="text/html; charset=%s">z<title>%s</title>
</head>z<body>
<h1>%s</h1>z <hr>
<ul>r �@z <li><a href="%s">%s</a></li>z</ul>
<hr>
</body>
</html>
�
�surrogateescaper z Content-typeztext/html; charset=%szContent-Length) r� �listdirr� r/ r r� �sortr� r� �unquoter4 �UnicodeDecodeErrorr �escaperk �getfilesystemencodingr_ rd r� �islinkZquoterU �io�BytesIOrY �seekrV r� rW r) r. rA )
r r4 �list�rZ displaypath�enc�title�name�fullnameZ displaynameZlinknameZencodedr� r r r
r� � s\
z'SimpleHTTPRequestHandler.list_directoryc C sB | j d d � d } | j d d � d } | j � j d � } y t j j | d d �} Wn$ t k
r� t j j | � } Yn Xt j | � } | j d � } t d | � } t
j � } xn | D]f } t
j j
| � \ } } t
j j | � \ } } | t
j t
j f k rq� t
j j | | � } q� W| r>| d 7} | S) z�Translate a /-separated PATH to the local filename syntax.
Components that mean special things to the local file system
(e.g. drive or directory names) are ignored. (XXX They should
probably be diagnosed.)
�?r r �#r r� r� N)r- r+ r� r� r� r� r� � posixpath�normpath�filterr� �getcwdr4 �
splitdrive�curdir�pardirrd )r r4 Ztrailing_slashr> ZwordZdrive�headr r r
r� � s(
z'SimpleHTTPRequestHandler.translate_pathc C s t j | | � d S)a� Copy all data between two file objects.
The SOURCE argument is a file object open for reading
(or anything with a read() method) and the DESTINATION
argument is a file object open for writing (or
anything with a write() method).
The only reason for overriding this would be to change
the block size or perhaps to replace newlines by CRLF
-- note however that this the default server uses this
to copy binary data as well.
N)�shutilZ copyfileobj)r �sourceZ
outputfiler r r
r�
s z!SimpleHTTPRequestHandler.copyfilec C sd t j | � \ } } | | j k r/ | j | S| j � } | | j k rU | j | S| j d Sd S)a� Guess the type of a file.
Argument is a PATH (a filename).
Return value is a string of the form type/subtype,
usable for a MIME Content-type header.
The default implementation looks the file's extension
up in the table self.extensions_map, using application/octet-stream
as a default; however it would be permissible (if
slow) to look inside the data to make a better guess.
r# N)r� �splitext�extensions_mapr; )r r4 �baseZextr r r
r� s z#SimpleHTTPRequestHandler.guess_typer# zapplication/octet-streamz.pyz
text/plainz.cz.hN)r r r r� r� rp r� r� r� r� r� r� r� � mimetypesZinitedZinitZ types_map�copyr� �updater r r r
r c s"
1 :
c C s+ | j d � \ } } } t j j | � } | j d � } g } xP | d d � D]> } | d k ro | j � qP | rP | d k rP | j | � qP W| r� | j � } | r� | d k r� | j � d } q� | d k r� d } n d } | r� d j | | f � } d d j | � | f } d j | � } | S) a�
Given a URL path, remove extra '/'s and '.' path elements and collapse
any '..' references and returns a collapsed path.
Implements something akin to RFC-2396 5.2 step 6 to parse relative paths.
The utility of this function is limited to is_cgi method and helps
preventing some security attacks.
Returns: The reconstituted URL, which will always start with a '/'.
Raises: IndexError if too many '..' occur within the path.
r� r Nr z..r! r# ���)� partitionr� r� r� r- �popr_ rd ) r4 �_�query�
path_partsZ
head_parts�partZ tail_partZ splitpath�collapsed_pathr r r
�_url_collapse_path? s.
r� c C s� t r
t Sy d d l } Wn t k
r2 d SYn Xy | j d � d a Wn5 t k
r� d t d d � | j � D� � a Yn Xt S) z$Internal routine to get nobody's uidr Nr �nobodyr c s s | ] } | d Vq d S)r Nr )r� r~ r r r
� <genexpr>} s z nobody_uid.<locals>.<genexpr>r� )r� �pwd� ImportError�getpwnamrS �maxZgetpwall)r� r r r
�
nobody_uidq s
(r� c C s t j | t j � S)zTest for executable file.)r� �access�X_OK)r4 r r r
�
executable� s r� c @ s e Z d Z d Z e e d � Z d Z d d � Z d d � Z d d � Z
d
d g Z d d
� Z d d � Z
d d � Z d S)r z�Complete HTTP server with GET, HEAD and POST commands.
GET and HEAD also support running CGI scripts.
The POST command is *only* implemented for CGI scripts.
�forkr c C s0 | j � r | j � n | j t j d � d S)zRServe a POST request.
This is only implemented for CGI scripts.
z Can only POST to CGI scriptsN)�is_cgi�run_cgir/ r rD )r r r r
�do_POST� s
z CGIHTTPRequestHandler.do_POSTc C s' | j � r | j � St j | � Sd S)z-Version of send_head that support CGI scriptsN)r� r� r r� )r r r r
r� � s
z CGIHTTPRequestHandler.send_headc C sl t | j � } | j d d � } | d | � | | d d � } } | | j k rh | | f | _ d Sd S)a3 Test whether self.path corresponds to a CGI script.
Returns True and updates the cgi_info attribute to the tuple
(dir, rest) if self.path requires running a CGI script.
Returns False otherwise.
If any exception is raised, the caller should assume that
self.path was rejected as invalid and act accordingly.
The default implementation tests whether the normalized url
path begins with one of the strings in self.cgi_directories
(and the next character is a '/' or the end of the string).
r r NTF)r� r4 �find�cgi_directories�cgi_info)r r� Zdir_sepr� �tailr r r
r� � s %z CGIHTTPRequestHandler.is_cgiz/cgi-binz/htbinc C s
t | � S)z1Test whether argument path is an executable file.)r� )r r4 r r r
�
is_executable� s z#CGIHTTPRequestHandler.is_executablec C s( t j j | � \ } } | j � d k S)z.Test whether argument path is a Python script.�.py�.pyw)r� r� )r� r4 r� r; )r r4 r� r� r r r
� is_python� s z CGIHTTPRequestHandler.is_pythonc ) C s� | j \ } } | d | } | j d t | � d � } x� | d k r� | d | � } | | d d � } | j | � } t j j | � r� | | } } | j d t | � d � } q< Pq< W| j d � \ } } } | j d � } | d k r| d | � | | d � }
} n
| d }
} | d |
} | j | � } t j j | � sl| j t
j d | � d St j j | � s�| j t
j
d | � d S| j | � }
| j s�|
r�| j | � s�| j t
j
d | � d St j t j � } | j � | d
<| j j | d <d | d
<| j | d <t | j j � | d <| j | d <t j j | � } | | d <| j | � | d <| | d <| r�| | d <| j d | d <| j j d � } | r�| j! � } t | � d k r�d d l" } d d l# } | d | d <| d j$ � d k r�y/ | d j% d � } | j& | � j' d � } Wn | j( t) f k
rfYn0 X| j! d � } t | � d k r�| d | d <| j j d � d k r�| j j* � | d <n | j d | d <| j j d � } | r�| | d <| j j d! � } | r| | d" <g } xc | j j+ d# � D]O } | d d � d$ k rd| j, | j- � � q2| | d% d � j! d& � } q2Wd& j. | � | d' <| j j d( � } | r�| | d) <t/ d | j j0 d* g � � } d+ j. | � } | r�| | d, <x d@ D] } | j1 | d � q�W| j2 t
j3 d. � | j4 � | j5 d/ d0 � } | j r�|
g } d1 | k rr| j, | � t6 � } | j7 j8 � t j9 � } | d k rt j: | d � \ } } x9 t; j; | j< g g g d � d r�| j< j= d � s�Pq�W| r
| j> d2 | � d Syo y t j? | � Wn t@ k
r6Yn Xt jA | j< jB � d � t jA | j7 jB � d � t jC | | | � Wq�| j jD | jE | j � t jF d3 � Yq�Xnd d lG } | g }! | j | � r!tH jI }" |" j$ � jJ d4 � r|" d dA � |" dB d � }" |" d7 g |! }! d1 | k r:|! j, | � | jK d8 | jL |! � � y tM | � }# Wn tN tO f k
r�d }# Yn X| jP |! d9 | jQ d: | jQ d; | jQ d< | �}$ | j j$ � d= k r�|# d k r�| j< j= |# � }% n d }% x? t; j; | j< jR g g g d � d r1| j< jR jS d � s�Pq�W|$ jT |% � \ }& }' | j7 jU |& � |' rm| j> d> |' � |$ jV jW � |$ jX jW � |$ jY }( |( r�| j> d2 |( � n
| jK d? � d S)CzExecute a CGI script.r r r Nr� r# zNo such CGI script (%r)z#CGI script is not a plain file (%r)z!CGI script is not executable (%r)ZSERVER_SOFTWAREZ SERVER_NAMEzCGI/1.1ZGATEWAY_INTERFACEZSERVER_PROTOCOLZ SERVER_PORTZREQUEST_METHODZ PATH_INFOZPATH_TRANSLATEDZ SCRIPT_NAME� QUERY_STRINGZ REMOTE_ADDR�
authorizationr Z AUTH_TYPEZbasic�ascii�:Z REMOTE_USERz content-typeZ CONTENT_TYPEzcontent-length�CONTENT_LENGTH�referer� HTTP_REFERER�acceptz
� �,Z HTTP_ACCEPTz
user-agent�HTTP_USER_AGENTZcookiez, � HTTP_COOKIE� REMOTE_HOSTzScript output follows�+ro �=zCGI script exit status %#x� zw.exer r� z-uz command: %s�stdin�stdoutrl �envZpostz%szCGI script exited OK)r� r� r� r� r� r� ������)Zr� r� r. r� r� r4 r� r� r� r/ r r� �isfileZ FORBIDDENr� � have_forkr� r� �deepcopy�environr[ Zserverr r3 r) r r% r� r� r� r r9 r: r- �base64�binasciir; rU Z decodebytes�decode�Error� UnicodeErrorZget_content_typeZgetallmatchingheadersr_ �striprd r� Zget_all�
setdefaultrV r� rb r
r� rF rG r� �waitpid�selectr7 �readrH �setuidr� �dup2r� �execveZ handle_errorZrequest�_exit�
subprocessrk r� r� rg Z list2cmdliner1 � TypeErrorr0 �Popen�PIPEZ_sockZrecvZ communicaterY rl r$ r� �
returncode))r �dir�restr4 �iZnextdirZnextrestZ scriptdirr� r� ZscriptZ
scriptnameZ
scriptfileZispyr Zuqrestr� r r Zlengthr� r� �lineZua�coZ
cookie_str�kZ
decoded_queryrj r� �pid�stsr ZcmdlineZinterp�nbytes�p�datar� rl Zstatusr r r
r� � s4
$
!
%
!(
z CGIHTTPRequestHandler.run_cgiN)r r r r� rC r� r Zrbufsizer� r� r� r� r� r� r� r r r r
r � s zHTTP/1.0i@ r# c C s� | | f } | | _ | | | � } | j j � } t d | d d | d d � y | j � Wn3 t k
r� t d � | j � t j d � Yn Xd S)zmTest the HTTP request handler class.
This runs an HTTP server on port 8000 (or the port argument).
zServing HTTP onr r r z...z&
Keyboard interrupt received, exiting.N) r3 r r �printZ
serve_forever�KeyboardInterruptZ server_closerk �exit)� HandlerClassZ ServerClassZprotocolr �bindZserver_addressZhttpdZsar r r
�test� s
r* �__main__z--cgi�action�
store_true�helpzRun as CGI Serverz--bindz-b�default�metavarZADDRESSz8Specify alternate bind address [default: all interfaces]r Zstore�type�nargsr� z&Specify alternate port [default: 8000]r( r) ).r� r� �__all__r Z http.clientr5 r� r� r� r� r r� r r rk rr Z urllib.parser� r� �argparser r� r� r r r ZStreamRequestHandlerr r r� r� r� r� r r* r �ArgumentParser�parser� add_argumentr1 �
parse_argsrj ZcgiZ
handler_classr r) r r r r
�<module> sb 3 � �� 0 �
Rosenblum TV: Video training, virtual workshops, classes, tutorials
RE-INVENTING THE TELEVISION NEWS BUSINESS*
A revolution in video storytelling
Creating entirely new & cost-effective production methods
From the world leaders in video production training and the creators of Character Driven Storytelling™
*and every other business that uses video
WHAT WE DO
Over the past 35 years, we have designed, built or restructured some of the most powerful news and journalism companies in the world.
We replace the traditional TV news ‘crew’ with one highly trained journalist, working alone with nothing but an iPhone.
No more TV news ‘crews’, no editors and no field producers.
This is television news done the way newspaper journalism is done – one reporter with their electronic pad and pencil.
In doing this, we can cut the cost of production by as much as 75% while increasing ratings and audience engagement.
In the place of conventional TV news ‘packages’ – ie, reporter stand up, interview, b-roll, man on the street, we marry great journalism with Netflix and Hollywood storytelling.
It’s a combination that works.
We have taken most of our clients to #1 in their respective markets.
And it’s not just for news. Any company, any profit, any NGO and anyone else who is online needs to tell their story in compelling yet cost-effective video. We can teach you to do that. Either in person or virtually.
EXAMPLES OF WHAT WE CAN TEACH YOUR STAFF TO PRODUCE
ITAY HOD
Itay Hod, MMJ with KPIX/CBS in San Francisco, took the 5-Day Intensive Video Storytelling Bootcamp in 2018.
Because he works alone, with only an iPhone, he was able to embed himself with a homeless family.
Here’s the story he produced in a one-day turn.
KIET DO
Kiet Do, an MMJ with KPIX/CBS in San Francisco, took the 5-Day Intensive Video Storytelling Bootcamp in 2021.
Here is a story he produced, all on his own, with only an iPhone and in a one-day turn.
TAYLOR SCHAUB
Taylor Schaub, an MMJ with Spectrum News 1 in LA, took the 5-Day Intensive Video Storytelling Bootcamp in 2023.
Here is a story he turned in only one day, using only an iPhone. It was the first video story he ever did and it was nominated for an Emmy.
THE BOOTCAMP
How do we convert stations and whole networks to working in this way?
Since 1988, we have run intensive 5-Day Video Storytelling Bootcamps
We have done these all over the world.
These are hands-on bootcamps, and participants learn an entirely new way of creating TV news stories.
-We shoot at a 3:1 ratio or lower, so turnaround times are fast.
-We go directly from camera to timelilne and edit – no written scripts. We work in the medium of pictures and sound.
-We are entirely character-driven.
-We are driven by pictures and real events.
-We are focused almost entirely on ’the viewer experience’.
Since 1988, more than 70,000 journalists around the world have taken our bootcamps, either in person on virtualy.
We have started to work with CBS News, bringing our ideas of character-driven storytelling to one of the most successful and biggest networks in the United States. Since beginning to work with them ratings have climbed and more importantly, audience engagement is through the ceiling.
We started New York Times Television in 1990 and it was the first paper to be brought into the world of TV. It quickly became one of the most successful non-fiction production companies in the United States. The series and documentaries we produced won many awards including multiple Emmys.
We have been working with the BBC since the year 2000 helping to convert their national news network to our visual storytelling technique. Most recently we have trained teams from their sports, documentaries, and comedy divisions to make character-driven stories using only smartphones.
For the past five years we have worked with Spectrum News to introduce and train their journalists on visual, character driven storytelling using smartphones helping to create a different kind of local news for their network of 24-Hour News Stations across the United States.
In 2006, we were approached by the United Nations. Rather than rely on news outlets, it would be much easier to train the field operatives to produce their own stories. We spent two years working with the UN, training more than 100 of their staff in bootcamps in Geneva and Nairobi.
We trained 50 print reporters at the paper to shoot and tell their own stories, in conjunction with their print work. We built a TV newsroom in their existing print newsroom – you could not ask for a better set and they began to live stream their stories in conjunction with their print work.
We spent two years with McGraw Hill, training more than 150 of their staffers, making them completely video literate. McGraw/Hill media properties we transit included Business Week, Aviation Week, (what was the name of the architecture magazine), and JD Power and Associates.
In 1990, we were approached by The Voice of America, the official broadcasting agency for the United States Government. When we met with VOA, they were only a short wave radio broadcaster, but working with them, we took them into television, launching VOA-TV.
British based Oyster Yachts makes some of the finest yachts in the world. Like every other company, they had to find a way to feed the never-ending video demands of social media – sites like Instagram and TikTok. We trained the Oyster staff to tell their own stories, using only iPhones.
We were approached by SEPA, the Scottish Environmental Protection Agency because they had to continually find a way to ‘feed the media beast’. The result was that SEPA was able to tell their own stories, whenever they wanted, and at almost no additional cost.
Michael Rosenblum has been writing about the media since 1988. His work and ideas have appeared in The Guardian, The Huffington Post, Ilkeston Life and many other publications.
He has been blogging regularly for the past 35 years on this subject. Having taught media studies at Columbia University, NYU and now the University of Oxford, he is considered an expert on this subject.
Continue reading this post or look back at previous posts.
