Operation   : Linux premium131.web-hosting.com 4.18.0-553.44.1.lve.el8.x86_64 #1 SMP Thu Mar 13 14:29:12 UTC 2025 x86_64
Software     : Apache
Server IP    : 162.0.232.56 | Your IP: 216.73.216.111
Domains      : 1034 Domain(s)
Permission   : [ 0755 ]

B

� f+i�	@s�
dZd
Z
ddlZddlZddlZddlZddlZddlmZ
ddl	m
Z	
dddd	d
ddd
dg	Zeed�rxe�
dddg�

eed�r�e�
ddddg�

eed�r�ejZnejZGdd�d�ZGdd�de�ZGdd�de�Zeed�r�Gdd�d�ZGdd�d�Zeed��
r0Gdd�dee�ZGdd�dee�ZGd d	�d	ee�ZGd!d
�d
ee�Zeed��
r�Gd"d�de�ZGd#d�de�ZGd$d�dee�ZGd%d�dee�ZGd&d�d�ZGd'd�de�ZGd(d)�d)e�Z Gd*d
�d
e�Z!dS)+aqGeneric socket server classes.

This module tries to capture the various aspects of defining a server:

For socket-based servers:

- address family:
        - AF_INET{,6}: IP (Internet Protocol) sockets (default)
        - AF_UNIX: Unix domain sockets
        - others, e.g. AF_DECNET are conceivable (see <socket.h>
- socket type:
        - SOCK_STREAM (reliable stream, e.g. TCP)
        - SOCK_DGRAM (datagrams, e.g. UDP)

For request-based servers (including socket-based):

- client address verification before further looking at the request
        (This is actually a hook for any processing that needs to look
         at the request before anything else, e.g. logging)
- how to handle multiple requests:
        - synchronous (one request is handled at a time)
        - forking (each request is handled by a new process)
        - threading (each request is handled by a new thread)

The classes in this module favor the server type that is simplest to
write: a synchronous TCP/IP server.  This is bad class design, but
saves some typing.  (There's also the issue that a deep class hierarchy
slows down method lookups.)

There are five classes in an inheritance diagram, four of which represent
synchronous servers of four types:

        +------------+
        | BaseServer |
        +------------+
              |
              v
        +-----------+        +------------------+
        | TCPServer |------->| UnixStreamServer |
        +-----------+        +------------------+
              |
              v
        +-----------+        +--------------------+
        | UDPServer |------->| UnixDatagramServer |
        +-----------+        +--------------------+

Note that UnixDatagramServer derives from UDPServer, not from
UnixStreamServer -- the only difference between an IP and a Unix
stream server is the address family, which is simply repeated in both
unix server classes.

Forking and threading versions of each type of server can be created
using the ForkingMixIn and ThreadingMixIn mix-in classes.  For
instance, a threading UDP server class is created as follows:

        class ThreadingUDPServer(ThreadingMixIn, UDPServer): pass

The Mix-in class must come first, since it overrides a method defined
in UDPServer! Setting the various member variables also changes
the behavior of the underlying server mechanism.

To implement a service, you must derive a class from
BaseRequestHandler and redefine its handle() method.  You can then run
various versions of the service by combining one of the server classes
with your request handler class.

The request handler class must be different for datagram or stream
services.  This can be hidden by using the request handler
subclasses StreamRequestHandler or DatagramRequestHandler.

Of course, you still have to use your head!

For instance, it makes no sense to use a forking server if the service
contains state in memory that can be modified by requests (since the
modifications in the child process would never reach the initial state
kept in the parent process and passed to each child).  In this case,
you can use a threading server, but you will probably have to use
locks to avoid two requests that come in nearly simultaneous to apply
conflicting changes to the server state.

On the other hand, if you are building e.g. an HTTP server, where all
data is stored externally (e.g. in the file system), a synchronous
class will essentially render the service "deaf" while one request is
being handled -- which may be for a very long time if a client is slow
to read all the data it has requested.  Here a threading or forking
server is appropriate.

In some cases, it may be appropriate to process part of a request
synchronously, but to finish processing in a forked child depending on
the request data.  This can be implemented by using a synchronous
server and doing an explicit fork in the request handler class
handle() method.

Another approach to handling multiple simultaneous requests in an
environment that supports neither threads nor fork (or where these are
too expensive or inappropriate for the service) is to maintain an
explicit table of partially finished requests and to use a selector to
decide which request to work on next (or whether to handle a new
incoming request).  This is particularly important for stream services
where each client can potentially be connected for a long time (if
threads or subprocesses cannot be used).

Future work:
- Standard classes for Sun RPC (which uses either UDP or TCP)
- Standard mix-in classes to implement various authentication
  and encryption schemes

XXX Open problems:
- What to do with out-of-band data?

BaseServer:
- split generic "request" functionality out into BaseServer class.
  Copyright (C) 2000  Luke Kenneth Casson Leighton <lkcl@samba.org>

  example: read entries from a SQL database (requires overriding
  get_request() to return a table entry from the database).
  entry is processed by a RequestHandlerClass.

z0.4�N)
�BufferedIOBase)
�	monotonic�
BaseServer�	TCPServer�	UDPServer�ThreadingUDPServer�ThreadingTCPServer�BaseRequestHandler�StreamRequestHandler�DatagramRequestHandler�ThreadingMixIn�fork�ForkingUDPServer�ForkingTCPServer�ForkingMixIn�AF_UNIX�UnixStreamServer�UnixDatagramServer�ThreadingUnixStreamServer�ThreadingUnixDatagramServer�PollSelectorc@s�eZ
dZd
ZdZdd�Zdd�Zd&dd	�
Zd
d�Zdd
�Z	dd�Z
dd�Zdd�Zdd�Z
dd�Zdd�Zdd�Zdd�Zdd�Zd d!�Zd"d#�Zd$d%�ZdS)'ra�Base class for server classes.

    Methods for the caller:

    - __init__(server_address, RequestHandlerClass)
    - serve_forever(poll_interval=0.5)
    - shutdown()
    - handle_request()  # if you do not use serve_forever()
    - fileno() -> int   # for selector

    Methods that may be overridden:

    - server_bind()
    - server_activate()
    - get_request() -> request, client_address
    - handle_timeout()
    - verify_request(request, client_address)
    - server_close()
    - process_request(request, client_address)
    - shutdown_request(request)
    - close_request(request)
    - service_actions()
    - handle_error()

    Methods for derived classes:

    - finish_request(request, client_address)

    Class variables that may be overridden by derived classes or
    instances:

    - timeout
    - address_family
    - socket_type
    - allow_reuse_address

    Instance variables:

    - RequestHandlerClass
    - socket

    NcCs |
|_||_
t��|_d
|_dS)z/Constructor.  May be extended, do not override.FN)�server_address�RequestHandlerClass�	threadingZEvent�_BaseServer__is_shut_down�_BaseServer__shutdown_request)�selfrr�r�1/opt/alt/python37/lib64/python3.7/socketserver.py�__init__�s



zBaseServer.__init__c


Csd
S)zSCalled by constructor to activate the server.

        May be overridden.

        Nr)
rrrr�server_activate�szBaseServer.server_activate��?c	Csx|j�
�
zVt��F}|�|tj�
x0|jsR|�|
�
}|jr<P|rH|��
|�	�
q$WWd
QRXWd
d|_|j�
�
Xd
S)z�Handle one request at a time until shutdown.

        Polls for shutdown every poll_interval seconds. Ignores
        self.timeout. If you need to do periodic tasks, do them in
        another thread.
        NF)r�clear�_ServerSelector�register�	selectors�
EVENT_READr�select�_handle_request_noblock�service_actions�set)rZ
poll_interval�selector�readyrrr�
serve_forever�s








zBaseServer.serve_foreverc

Csd
|_|j
��
dS)z�Stops the serve_forever loop.

        Blocks until the loop has finished. This must be called while
        serve_forever() is running in another thread, or it will
        deadlock.
        TN)rr�wait)
rrrr�shutdown�s
zBaseServer.shutdownc


Csd
S)z�Called by the serve_forever() loop.

        May be overridden by a subclass / Mixin to implement any code that
        needs to be run during the loop.
        Nr)
rrrrr)�szBaseServer.service_actionsc
	Cs�|j�
�}
|
d
kr|j}
n|jd
k	r0t|
|j�}
|
d
k	rBt�|
}t��R}|�|tj�
x<|�	|
�
}|rp|�
�S|
d
k	rZ|t�}
|
dkrZ|��SqZWWd
QRXd
S)zOHandle one request, possibly blocking.

        Respects self.timeout.
        Nr
)�socketZ
gettimeout�timeout�min�timer#r$r%r&r'r(�handle_timeout)rr1Zdeadliner+r,rrr�handle_request
s"

















zBaseServer.handle_requestc
Cs�y|��\}
}Wnt
k
r$


d
SX|�|
|�r�y|�|
|�
Wq�tk
rl


|�|
|�
|�|
�

Yq�


|�|
�

�Yq�Xn
|�|
�

d
S)z�Handle one request, without blocking.

        I assume that selector.select() has returned that the socket is
        readable before this function was called, so there should be no risk of
        blocking in get_request().
        N)�get_request�OSError�verify_request�process_request�	Exception�handle_error�shutdown_request)r�request�client_addressrrrr(/
s













z"BaseServer._handle_request_noblockc


Csd
S)zcCalled if no new request arrives within self.timeout.

        Overridden by ForkingMixIn.
        Nr)
rrrrr4F
szBaseServer.handle_timeoutc
Csd
S)znVerify the request.  May be overridden.

        Return True if we should proceed with this request.

        Tr)rr=r>rrrr8M
szBaseServer.verify_requestcCs|�|
|�
|�
|
�

d
S)zVCall finish_request.

        Overridden by ForkingMixIn and ThreadingMixIn.

        N)�finish_requestr<)rr=r>rrrr9U
s
zBaseServer.process_requestc


Csd
S)zDCalled to clean-up the server.

        May be overridden.

        Nr)
rrrr�server_close^
szBaseServer.server_closecCs|�|
||�
d
S)z8Finish one request by instantiating RequestHandlerClass.N)
r)rr=r>rrrr?f
szBaseServer.finish_requestcCs|�|
�

d
S)z3Called to shutdown and close an individual request.N)
�
close_request)rr=rrrr<j
szBaseServer.shutdown_requestc
Csd
S)z)Called to clean up an individual request.Nr)rr=rrrrAn
szBaseServer.close_requestcCs@td
t
jd�
td|t
jd�
ddl}|��
td
t
jd�
dS)ztHandle an error gracefully.  May be overridden.

        The default is to print a traceback and continue.

        z(----------------------------------------)
�filez4Exception happened during processing of request fromr
N)�print�sys�stderr�	traceback�	print_exc)rr=r>rFrrrr;r
s




zBaseServer.handle_errorc


Cs|S)
Nr)
rrrr�	__enter__
s
zBaseServer.__enter__c
Gs|��
dS)
N)
r@)r�argsrrr�__exit__�
s
zBaseServer.__exit__)
r!)�__name__�
__module__�__qualname__�__doc__r1rr r-r/r)r5r(r4r8r9r@r?r<rAr;rHrJrrrrr�s&+

	
c@sfeZ
dZd
ZejZejZdZ	dZ
ddd�
Zdd�Zd	d
�Z
dd�Zd
d�Zdd�Zdd�Zdd�ZdS)ra3Base class for various socket-based server classes.

    Defaults to synchronous IP stream (i.e., TCP).

    Methods for the caller:

    - __init__(server_address, RequestHandlerClass, bind_and_activate=True)
    - serve_forever(poll_interval=0.5)
    - shutdown()
    - handle_request()  # if you don't use serve_forever()
    - fileno() -> int   # for selector

    Methods that may be overridden:

    - server_bind()
    - server_activate()
    - get_request() -> request, client_address
    - handle_timeout()
    - verify_request(request, client_address)
    - process_request(request, client_address)
    - shutdown_request(request)
    - close_request(request)
    - handle_error()

    Methods for derived classes:

    - finish_request(request, client_address)

    Class variables that may be overridden by derived classes or
    instances:

    - timeout
    - address_family
    - socket_type
    - request_queue_size (only for stream sockets)
    - allow_reuse_address

    Instance variables:

    - server_address
    - RequestHandlerClass
    - socket

    �FTcCsTt�
||
|�
t�|j|j�|_|rPy|��
|��
Wn


|��
�YnXd
S)z/Constructor.  May be extended, do not override.N)rrr0�address_family�socket_type�server_bindr r@)rrrZbind_and_activaterrrr�
s









zTCPServer.__init__c

Cs8|jr|j
�t
jt
jd
�
|j
�|j�

|j
��|_dS)zOCalled by constructor to bind the socket.

        May be overridden.

        �
N)�allow_reuse_addressr0�
setsockoptZ
SOL_SOCKETZSO_REUSEADDRZbindrZgetsockname)
rrrrrR�
s


zTCPServer.server_bindc

Cs|j�
|j�

d
S)zSCalled by constructor to activate the server.

        May be overridden.

        N)r0Zlisten�request_queue_size)
rrrrr �
szTCPServer.server_activatec

Cs|j�
�
d
S)zDCalled to clean-up the server.

        May be overridden.

        N)r0�close)
rrrrr@�
szTCPServer.server_closec

Cs
|j�
�S)
zMReturn socket file number.

        Interface required by selector.

        )r0�fileno)
rrrrrX�
szTCPServer.filenoc

Cs
|j�
�S)
zYGet the request and client address from the socket.

        May be overridden.

        )r0Zaccept)
rrrrr6�
szTCPServer.get_requestcCs4y|
�t
j�

Wntk
r$


YnX|�|
�

d
S)z3Called to shutdown and close an individual request.N)r/r0ZSHUT_WRr7rA)rr=rrrr<�
s



zTCPServer.shutdown_requestcCs|
��
d
S)z)Called to clean up an individual request.N)
rW)rr=rrrrA�
szTCPServer.close_requestN)
T)rKrLrMrNr0ZAF_INETrPZSOCK_STREAMrQrVrTrrRr r@rXr6r<rArrrrr�
s-


c@s>eZ
dZd
ZdZejZdZdd�Z	dd�Z
dd	�Zd
d�ZdS)
rzUDP server class.Fi c
Cs |j�
|j�
\}
}|
|jf|fS)
N)r0Zrecvfrom�max_packet_size)r�dataZclient_addrrrrr6s

zUDPServer.get_requestc


CsdS)
Nr)
rrrrr szUDPServer.server_activatecCs|�|
�

dS)
N)
rA)rr=rrrr<szUDPServer.shutdown_requestc
CsdS)
Nr)rr=rrrrAszUDPServer.close_requestN)
rKrLrMrNrTr0Z
SOCK_DGRAMrQrYr6r r<rArrrrrscsVeZ
dZd
ZdZdZdZdZdd�
dd	�Zd
d�Z	dd
�Z
dd�Z�f
dd�Z�Z
S)rz5Mix-in class to handle each request in a new process.i,
N�(TF)
�blockingc

	Cs�|jd
krd
Sxht
|j�
|jkrvy t�dd�\}}|j�|�

Wqtk
r^


|j��
Yqtk
rr


PYqXqWxt|j�	�D]f}y.|
r�dntj
}t�||�\}}|j�|�

Wq�tk
r�


|j�|�

Yq�tk
r�


Yq�Xq�Wd
S)z7Internal routine to wait for children that have exited.N���r
)�active_children�len�max_children�os�waitpid�discard�ChildProcessErrorr"r7�copy�WNOHANG)rr\�pid�
_�flagsrrr�collect_children(s&













zForkingMixIn.collect_childrenc

Cs|��
d
S)zvWait for zombies after self.timeout seconds of inactivity.

            May be extended, do not override.
            N)
rj)
rrrrr4KszForkingMixIn.handle_timeoutc

Cs|��
d
S)z�Collect the zombie child processes regularly in the ForkingMixIn.

            service_actions is called in the BaseServer's serve_forever loop.
            N)
rj)
rrrrr)RszForkingMixIn.service_actionscCs�t�
�}|r8|jd
krt�|_|j�|�

|�|
�

d
Sd}z:y|�|
|�
d}Wn tk
rr


|�|
|�
YnXWd
z|�	|
�

Wd
t�
|�

XXd
S)z-Fork a new subprocess to process the request.NrSr
)rar
r^r*�addrAr?r:r;r<�_exit)rr=r>rgZstatusrrrr9Ys 












zForkingMixIn.process_requestc

st��
�
|j|jd
�

dS)N)
r\)�superr@rj�block_on_close)
r)
�	__class__rrr@rs


zForkingMixIn.server_close)rKrLrMrNr1r^r`rnrjr4r)r9r@�
__classcell__rr)
rorrs


#cs<eZ
dZd
ZdZdZdZdd�Zdd�Z�f
d	d
�Z	�Z
S)rz4Mix-in class to handle each request in a new thread.FTNc	CsHz6y|�|
|�
Wn t
k
r2


|�|
|�
YnXWd
|�|
�

Xd
S)zgSame as in BaseServer but as a thread.

        In addition, exception handling is done here.

        N)r?r:r;r<)rr=r>rrr�process_request_thread�s



z%ThreadingMixIn.process_request_threadcCsPtj
|j|
|fd
�}|j|_|jsD|jrD|jdkr8g|_|j�|�

|��
dS)z*Start a new thread to process the request.)�targetrIN)	rZThreadrq�daemon_threadsZdaemonrn�_threads�append�start)rr=r>�
trrrr9�s







zThreadingMixIn.process_requestc
s:t��
�
|jr6|j}
d|_|
r6x|
D]}|��
q&WdS)
N)rmr@rnrt�join)rZthreadsZthread)
rorrr@�s








zThreadingMixIn.server_close)rKrLrMrNrsrnrtrqr9r@rprr)
rorrws

c
@seZ
dZd
S)rN)rKrLrMrrrrr�sc
@seZ
dZd
S)rN)rKrLrMrrrrr�sc
@seZ
dZd
S)rN)rKrLrMrrrrr�sc
@seZ
dZd
S)rN)rKrLrMrrrrr�sc
@seZ
dZejZd
S)rN)rKrLrMr0rrPrrrrr�s
c
@seZ
dZejZd
S)rN)rKrLrMr0rrPrrrrr�s
c
@seZ
dZd
S)rN)rKrLrMrrrrr�sc
@seZ
dZd
S)rN)rKrLrMrrrrr�sc@s0eZ
dZd
Zdd�Zdd�Zdd�Zdd	�Zd
S)r	a�Base class for request handler classes.

    This class is instantiated for each request to be handled.  The
    constructor sets the instance variables request, client_address
    and server, and then calls the handle() method.  To implement a
    specific service, all you need to do is to derive a class which
    defines a handle() method.

    The handle() method can find the request as self.request, the
    client address as self.client_address, and the server (in case it
    needs access to per-server information) as self.server.  Since a
    separate instance is created for each request, the handle() method
    can define other arbitrary instance variables.

    cCs6|
|_||_
||_|��
z|��
Wd|��
XdS)
N)r=r>�server�setup�handle�finish)rr=r>ryrrrr�s





zBaseRequestHandler.__init__c


CsdS)
Nr)
rrrrrz�s
zBaseRequestHandler.setupc


CsdS)
Nr)
rrrrr{�s
zBaseRequestHandler.handlec


CsdS)
Nr)
rrrrr|�s
zBaseRequestHandler.finishN)rKrLrMrNrrzr{r|rrrrr	�s

c@s0eZ
dZd
ZdZdZdZdZdd�Zdd	�Z	dS)
r
z4Define self.rfile and self.wfile for stream sockets.r]r
NFc

Csz|j|_
|jdk	r |j
�|j�

|jr:|j
�tjtjd
�
|j
�	d|j
�|_|jdkrdt
|j
�
|_n|j
�	d|j�|_dS)NT�rbr
�wb)r=Z
connectionr1Z
settimeout�disable_nagle_algorithmrUr0ZIPPROTO_TCPZTCP_NODELAYZmakefile�rbufsize�rfile�wbufsize�
_SocketWriter�wfile)
rrrrrz�s












zStreamRequestHandler.setupc

CsF|jj
s.y|j��
Wntjk
r,


YnX|j��
|j��
dS)
N)r��closed�flushr0�errorrWr�)
rrrrr|s






zStreamRequestHandler.finish)
rKrLrMrNr�r�r1rrzr|rrrrr
�s	

c@s0eZ
dZd
Zdd�Zdd�Zdd�Zdd	�Zd
S)r�z�Simple writable BufferedIOBase implementation for a socket

    Does not hold data in a buffer, avoiding any need to call flush().cCs
|
|_dS)
N)
�_sock)rZsockrrrrs
z_SocketWriter.__init__c


Csd
S)NTr)
rrrr�writables
z_SocketWriter.writablec	Cs&|j�
|
�

t|
�
�}|jSQRXdS)
N)r�Zsendall�
memoryview�nbytes)r�
bZviewrrr�writes



z_SocketWriter.writec

Cs
|j�
�S)
N)r�rX)
rrrrrX#s
z_SocketWriter.filenoN)rKrLrMrNrr�r�rXrrrrr�s
r�c@s eZ
dZd
Zdd�Zdd�ZdS)rz6Define self.rfile and self.wfile for datagram sockets.c
Cs2d
dlm
}

|j\|_|_|
|j�
|_|
�|_dS)Nr
)
�BytesIO)�ior�r=Zpacketr0r�r�)rr�rrrrz*s



zDatagramRequestHandler.setupc

Cs|j�
|j��|j�
dS)
N)r0Zsendtor��getvaluer>)
rrrrr|0s
zDatagramRequestHandler.finishN)rKrLrMrNrzr|rrrrr&s)"rN�__version__r0r%rarDrr�rr3r�__all__�hasattr�extendrr#ZSelectSelectorrrrrrrrrrrrrrr	r
r�rrrrr�<module>wsT


















n~

X.


.-