Skip to content

Module ciocore.auth.server

Functions

retry_loop

Source 
def retry_loop(server):
    while True:
        try:
            return socketserver.TCPServer.handle_request(server)
        except (OSError, select.error) as e:
            if e.args[0] != errno.EINTR:
                raise
retry_loop(server)

run

Source 
def run(server_class=HTTPServer, handler_class=Handler, port=8085, creds_file=None):
    global __credentials_file__
    global __keep_running__
    __credentials_file__ = creds_file
    __keep_running__ = True

    server_address = ("localhost", port)
    server_class.handle_request = retry_loop
    httpd = server_class(server_address, handler_class)
    httpd.timeout = REQUEST_TIMEOUT
    timeout = time.time() + SESSION_TIMEOUT
    while time.time() < timeout and __keep_running__:
        httpd.handle_request()
run(server_class=http.server.HTTPServer, handler_class=ciocore.auth.server.Handler, port=8085, creds_file=None)

Classes

Handler

Handler(request, client_address, server)

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

where is a (case-sensitive) keyword such as GET or POST, is a string containing path information for the request, and should be the string "HTTP/1.0" or "HTTP/1.1". 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

(i.e. 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

where is the protocol version ("HTTP/1.0" or "HTTP/1.1"), is a 3-digit response code indicating success or failure of the request, and 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 (). 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: /

where and should be registered MIME types, e.g. "text/html" or "text/plain".

Ancestors (in MRO)

  • http.server.BaseHTTPRequestHandler
  • socketserver.StreamRequestHandler
  • socketserver.BaseRequestHandler

Methods

do_POST

Source 
def do_POST(self):
    self._set_headers()

do_POST(self) :

do_GET

Source 
def do_GET(self):
    global __keep_running__
    #  Handle arg string
    self._set_headers()
    url_args = parse.parse_qs(parse.urlsplit(self.path).query)

    if "access_token" not in url_args:
        return

    credentials_dict = {
        "access_token": url_args["access_token"][0],
        "token_type": "Bearer",
        "expiration": int(time.time()) + int(url_args["expires_in"][0]),
        "scope": url_args["scope"],
    }
    self._write_credentials(credentials_dict)
    try:
        self.wfile.write(bytes(HTML, encoding="utf8"))
    except:
        self.wfile.write(HTML)

    __keep_running__ = False
    return

do_GET(self) :

log_message

Source 
def log_message(self, format, *args):
    return
log_message(self, format, *args)

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.

Back to top