diff --git a/Makefile b/Makefile index 5ff15b4..b6f2dcd 100644 --- a/Makefile +++ b/Makefile @@ -1,4 +1,4 @@ -PYROBUSTA_VERSION := v0.8.0 +PYROBUSTA_VERSION := v0.9.0 DEVICE ?= u0 SRC_DIR := src diff --git a/dist/pyrobusta/__init__.py b/dist/pyrobusta/__init__.py index e69de29..a82c93f 100644 --- a/dist/pyrobusta/__init__.py +++ b/dist/pyrobusta/__init__.py @@ -0,0 +1,6 @@ +"""Global server attributes""" + +from os import getcwd + +PYROBUSTA_VERSION = "v0.9.0" +WORKING_DIR = getcwd().rstrip("/") diff --git a/dist/pyrobusta/application.mpy b/dist/pyrobusta/application.mpy new file mode 100644 index 0000000..07d5ada Binary files /dev/null and b/dist/pyrobusta/application.mpy differ diff --git a/dist/pyrobusta/assets/www/concepts.html b/dist/pyrobusta/assets/www/concepts.html index b079661..581387d 100644 --- a/dist/pyrobusta/assets/www/concepts.html +++ b/dist/pyrobusta/assets/www/concepts.html @@ -8,7 +8,7 @@

Concepts

← Back

-

This chapter introduces the architectural concepts and design principles that underpin PyRobusta. +

This page introduces the architectural concepts and design principles that underpin PyRobusta. Detailed information about configuration, routing, and request handling is covered in the corresponding chapters.

Table of Contents

@@ -67,8 +67,9 @@

Execution Model

and associates each connection with a StreamReader and StreamWriter pair for network I/O.

Each client connection executes as an independent asynchronous task, allowing multiple connections to make progress concurrently. HttpServer maintains the set of active connections and accepts -new connections until the configured maximum number of concurrent connections is reached. HttpServer -closes idle connections after the configured timeout to reclaim resources. Because each connection is +new connections until the configured maximum number of concurrent connections is reached. When the +server is at capacity, new connections wait for resources to become available until a configurable +timeout expires. If the timeout is reached, the connection is rejected. Because each connection is processed independently, slow clients do not block unrelated connections. However, requests within the same connection are always processed sequentially.

HandlerHttpEngineHttpConnectionHttpServerClientHandlerHttpEngineHttpConnectionHttpServerClientloop[Until request complete]alt[Keep-Alive][Connection closed]New connectionReserve stream buffersCreate async connection taskProcess received bytesNeed more dataRead socketInvoke route handlerReturn responseResponse readySend responseWait for next requestRelease stream buffers

@@ -79,7 +80,8 @@

Memory Model

for normal request processing is reserved when a connection is accepted, rather than during request handling.

For each new connection, the server reserves a request and response stream buffer from the shared buffer pool. When all stream buffers are reserved, new connections are blocked until a buffer pair becomes available -(either through connection closure or timeout). HttpServer automatically closes connections that remain inactive for too long.

+(either through connection closure or timeout). Connections that remain inactive for too long will +automatically time out, enforced by HttpConnection.

Stream buffers are preallocated during server initialization based on the configured memory limits. Their size and number remain fixed throughout the lifetime of the server. Preallocating stream buffers reduces heap fragmentation, improving memory stability and reducing the risk of runtime allocation failures.

@@ -121,7 +123,7 @@

Resource Usage

Together, these architectural decisions enable PyRobusta to handle HTTP requests with predictable resource usage, incremental request processing, and deterministic behavior suitable for resource-constrained embedded systems.

-

PyRobusta v0.8.0 Web Server

+

PyRobusta v0.9.0 Web Server

diff --git a/dist/pyrobusta/assets/www/configuration.html b/dist/pyrobusta/assets/www/configuration.html index ede073f..617fee5 100644 --- a/dist/pyrobusta/assets/www/configuration.html +++ b/dist/pyrobusta/assets/www/configuration.html @@ -18,7 +18,7 @@

Table of Contents

  • Configuration
  • Configuration Format & Deployment
  • Parameter Description
    • -
  • Configuration API
    • +
  • Configuration Loading

    • Configuration Format & Deployment

    @@ -32,8 +32,8 @@

    Configuration Format & Deployment

    Perform a soft reset and upload pyrobusta.env using mpremote.

    -
    $ mpremote a0 soft-reset
-$ mpremote a0 cp pyrobusta.env :/pyrobusta.env
+
    $ mpremote connect /dev/ttyACM1 soft-reset
+$ mpremote connect /dev/ttyACM1 cp pyrobusta.env :/pyrobusta.env
 
    
 
    Parameter Description
    
 
@@ -52,10 +52,55 @@ 
    Parameter Description
    
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -67,65 +112,63 @@ 
    Parameter Description
    
-
+
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
-
-
+
+
+
+
+
+
+
-
-
-
+
+
+
+
+
+
+
+
    
 
 
    
 wifi_passwordPassword of the Wi-Fi network. When empty, Wi-Fi is not initialized by the built-in wifi.py module.Password of the Wi-Fi network.
 None
 
    
 
    tlsEnables or disables TLS. When enabled, cert.der and key.der must be installed at the server root.False
    tls_cert_fileAlternative path to the TLS certificate./cert.der
    tls_key_fileAlternative path to the TLS private key./key.der
    passwd_filePath to the file containing user credentials used for authentication./pyrobusta.passwd
    roles_filePath to the file containing RBAC role definitions used for authorization./pyrobusta.roles
    log_levelLogging level. Can be one of: error, warning, info, debug.info
    socket_max_conMaximum number of simultaneous socket connections.2
    http_served_pathsSpace-separated list of filesystem paths that may be served over HTTP./www
    http_mem_capFraction of available heap memory reserved for stream buffers. Valid range: (0, 1].0.1
    
 http_port
 Port number for HTTP.
 80
 
    
 
    
 http_multipartEnables or disables multipart request and response processing. Enabling multipart support increases memory usage.Enables or disables multipart request and response processing (Content-Type: multipart/*).
 False
 
    
 
    http_mem_capFraction of available heap memory reserved for stream buffers. Valid range: (0, 1].0.1
    http_served_pathsSpace-separated list of filesystem paths that may be served over HTTP./www /lib/pyrobusta
    
 http_files_api
 Enables or disables the file management API endpoint (/files), allowing upload, download, and listing of files.
 False
 
    
 
    socket_max_conMaximum number of simultaneous socket connections.2http_authSelects the type of authentication method enforced by the server. Currently, basic authentication (basic) is supported.None
 
    
 
    tlsEnables or disables TLS. When enabled, cert.der and key.der must be installed at the server root.http_browser_securityEnables or disables browser security features including browser security headers (Content Security Policy, referrer policy) and CSRF protection (if authentication is enabled). Disabling browser security is only recommended when using non-browser clients or during local development and testing.True
    http_insecure_authAllows clients to authenticate over unsecured HTTP (without TLS). This may expose credentials or authentication tokens in transit.
 False
 
    
 
    log_levelLogging level. Can be one of: warning, info, debug.infohttp_sessionsEnables browser session cookies for authenticated clients. When enabled, successful authentication establishes a session that can be reused without resending authentication credentials.True
    http_session_ttl_secDuration of validity of session cookies in seconds.900
 
    
     
 
    
-
    Configuration API
    
-
    Configuration values can be accessed through the
-pyrobusta.utils.config module.
-Values are loaded from pyrobusta.env during server initialization.
-Configuration values can be retrieved using
-get_config() together with one of the
-predefined CONF_* constants.
    
-
    After initialization, configuration values are retrieved from an internal cache.
-The cached values are normalized to their expected runtime types to avoid repeated
-parsing of environment strings.
    
-
    Configuration values are treated as immutable during runtime.
-Changes are applied only when the configuration cache is reloaded.
-The configuration cache can be reloaded by calling
-read_config(), which re-reads pyrobusta.env
-and rebuilds the internal normalized cache.
    
-
    from pyrobusta.utils.config import get_config, CONF_TLS
+
    Configuration Loading
    
+
    Configuration is represented by the Config class in
+pyrobusta.utils.config. During application initialization,
+pyrobusta.application creates and loads a Config instance from
+pyrobusta.env, converting values to their expected runtime types.
    
+
    Configuration values are exposed as attributes on the Config instance:
    
+
    config = Config("/pyrobusta.env")
 
-@HttpEngine.route("/tls", "GET")
-def tls_status(http_ctx, _):
-    enabled = get_config(CONF_TLS)
-    return "text/plain", f"TLS enabled: {enabled}"
+if config.tls:
+    ...
 
    
+
    The application uses the configuration to initialize and specialize the
+relevant subsystems during startup. The Config instance is then discarded;
+runtime components do not access configuration directly.
    
+
    Configuration is immutable for the lifetime of an application. Changes
+to pyrobusta.env therefore require a new application instance and, under
+normal operation, an application restart.
    
+
    The pyrobusta.utils.config module does not maintain a global configuration
+object or runtime configuration cache. It provides the Config definition
+and configuration-loading functionality.
    
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/assets/www/error_handling.html b/dist/pyrobusta/assets/www/error_handling.html
new file mode 100644
index 0000000..92a5756
--- /dev/null
+++ b/dist/pyrobusta/assets/www/error_handling.html
@@ -0,0 +1,152 @@
+
+
+
+
+
+
+
+
+
    Logging & Error Handling
    
+
    ← Back
    
+
    This page describes how the server provides logging with different levels of verbosity
+and handles HTTP status codes for client and server errors, including exceptions raised by applications.
    
+
    
+
    Table of Contents
    
+
+
    
+
    Logging
    
+
    The server provides built-in logging constructs implemented by the pyrobusta.utils.logging
+module. The logging module supports several log levels, controlled by the log_level server
+configuration. log_level can be set to one of error, warning, info, or debug, listed in increasing
+order of verbosity. Selecting a log level enables logging for that level and all less verbose levels.
+For example, setting log_level to info enables info, warning, and error messages.
    
+
    Logging methods expect a mandatory format string as the first positional argument,
+followed by optional positional arguments substituted in the format string.
    
+
    import asyncio
+
+from pyrobusta import application
+from pyrobusta.utils import logging
+
+
+async def main():
+  await application.run()
+  logging.info("%s: %s", __name__, "the application started")
+  while True:
+    await asyncio.sleep(1)
+
+asyncio.run(main())
+
    
+
    29972 INFO pyrobusta.application: connected, ip=[192.168.1.101]
+29983 INFO pyrobusta.server.http_server: 1 connection(s) allowed
+30029 INFO pyrobusta.server.http_server: started
+30041 INFO __main__: the application started
+
    
+
    Client Errors (4xx)
    
+
    As described in the Response Handling guide, route
+handlers can set the status codes directly with the terminate method of the HTTP
+context. Invalid requests should be rejected by the application with a 4xx status
+code. The specific status code is application-specific.
    
+
    @HttpEngine.route("/app/action", "POST")
+def handler(http_ctx, _):
+    content_type = http_ctx.headers.get("content-type")
+    if content_type != "application/json":
+      http_ctx.terminate(415)
+      return "text/plain", "Unsupported media"
+    # <rest of the application route>
+
    
+
    The application must use one of the following status codes supported by PyRobusta:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    Status CodeHTTP Status
    400Bad Request
    401Unauthorized
    403Forbidden
    404Not Found
    405Method Not Allowed
    408Request Timeout
    413Content Too Large
    415Unsupported Media Type
    
+
    Server Errors (5xx)
    
+
    5xx status codes indicate errors preventing the server from processing a valid request.
+The following list of 5xx status codes are supported by PyRobusta:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    Status CodeHTTP Status
    500Internal Server Error
    503Service Unavailable
    505Version Not Supported
    
+
    Exception Handling
    
+
    Applications may raise exceptions to signal a failure. Uncaught exceptions are
+automatically mapped to the 500 status code sent in the response.
    
+
    Additionally, when the server catches an exception raised by the application,
+it logs an error message.
    
+
    @HttpEngine.route("/app/action", "POST")
+def handler(http_ctx, _):
+    # [...]
+    raise RuntimeError("failed to execute action")
+    # [...]
+
    
+
    2287169 INFO pyrobusta.application: already connected ip=[192.168.1.101]
+2287179 INFO pyrobusta.server.http_server: 1 connection(s) allowed
+2287222 INFO pyrobusta.server.http_server: started
+[...]
+2292844 ERROR pyrobusta.protocol.http.run: error=[failed to execute action]
+
    
+
    
+
    PyRobusta v0.9.0 Web Server
    
+
+
+
diff --git a/dist/pyrobusta/assets/www/file_server.html b/dist/pyrobusta/assets/www/file_server.html
index a54fe4f..4ea4d72 100644
--- a/dist/pyrobusta/assets/www/file_server.html
+++ b/dist/pyrobusta/assets/www/file_server.html
@@ -139,7 +139,7 @@ 
    Example Request
    
 192.168.1.100/files/www/user_data/test.txt
 
    
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/assets/www/index.html b/dist/pyrobusta/assets/www/index.html
index 78418ba..84a685e 100644
--- a/dist/pyrobusta/assets/www/index.html
+++ b/dist/pyrobusta/assets/www/index.html
@@ -23,10 +23,12 @@ 
    Available Resources
    
 
  • Response Processing
    • 
 
  • Static Content
    • 
 
  • File Server API
    • 
+
  • Authentication & Security
    • 
+
  • Logging & Error Handling
    • 
 
  • Source Code
    • 
 
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/assets/www/introduction.html b/dist/pyrobusta/assets/www/introduction.html
index b6b1d97..fed0328 100644
--- a/dist/pyrobusta/assets/www/introduction.html
+++ b/dist/pyrobusta/assets/www/introduction.html
@@ -21,9 +21,10 @@ 
    Demo Application
    
 
    The following application demonstrates the basic structure of a PyRobusta application, including route registration,
 response generation, and server initialization. The application implements a simple HTTP API that returns the application version.
 The example includes boot.py, which starts the application, and app.py, which registers routes and starts the HTTP server.
    
-
    import asyncio
+
    # /app.py
+import asyncio
 
-from pyrobusta.server import http_server
+from pyrobusta import application
 from pyrobusta.protocol.http import HttpEngine
 
 APP_VERSION = "v0.1.0"
@@ -34,61 +35,52 @@ 
    Demo Application
    
         return "application/json", {
             "version": APP_VERSION
         }
-
     return "text/plain", f"{APP_VERSION}\n"
 
 async def main():
-    server = http_server.HttpServer()
-    await server.start_socket_server()
-
+    await application.run()
     while True:
         await asyncio.sleep(1)
 
    
-
    # /boot.py
+
    # /boot.py
 # This file is executed on every boot
 
+import asyncio
 import machine
-from os import listdir
-
-from pyrobusta.connectivity import wifi
-
-connected = wifi.initialize()
-if connected and not machine.reset_cause() == machine.SOFT_RESET:
-    if "app.py" in listdir():
-        import app
+import app
 
-        asyncio.run(app.main())
+if machine.reset_cause() != machine.SOFT_RESET:
+    asyncio.run(app.main())
 
    
 
    In the example, boot.py conditionally starts the server when no REPL session is active.
 This allows mpremote to connect after a soft reset and upload files during development.
    
 
    Deployment with mpremote
    
-
    Perform a soft reset and upload app.py and boot.py using mpremote.
    
-
    $ mpremote a0 soft-reset
-$ mpremote a0 cp app.py :/app.py
-$ mpremote a0 cp boot.py :/boot.py
+
    Perform a soft reset and upload app.py and boot.py using mpremote:
    
+
    $ mpremote connect /dev/ttyACM1 soft-reset
+$ mpremote connect /dev/ttyACM1 cp app.py :/app.py
+$ mpremote connect /dev/ttyACM1 cp boot.py :/boot.py
 
    
-
    Perform a hard reset to start the application and connect to the REPL.
    
-
    $ mpremote a0 reset repl
-Connected to MicroPython at /dev/ttyACM0
-...
-[INFO] pyrobusta.con.wifi: network b'Home-Wi-Fi' found!
-[INFO] pyrobusta.con.wifi: connected, available at 192.168.1.101
-[WARN] pyrobusta.server.http_server.init_pools: low-memory mode with reduced buffer size
-[INFO] pyrobusta.server.http_server.init_pools: 2 connection(s) allowed
-[INFO] pyrobusta.server.http_server: started
+
    Perform a hard reset to start the application and connect to the REPL:
    
+
    $ mpremote connect /dev/ttyACM1 reset sleep 1 repl
+Connected to MicroPython at /dev/ttyACM1
+Use Ctrl-] or Ctrl-x to exit this shell
+[...]
+2711 INFO pyrobusta.application: connected, ip=[192.168.1.101]
+2732 INFO pyrobusta.server.http_server: 4 connection(s) allowed
+2762 INFO pyrobusta.server.http_server: started
 
-# You can now reach the device at 192.168.1.101 (replace with your IP)
+# You can now reach the device at the indicated IP address
 # Press Ctrl-x to exit
 
    
-
    Use curl to test the application.
    
-
    $ curl "http://192.168.1.101/version"
+
    Use curl to test the application:
    
+
    $ curl "http://192.168.1.101/version"
 v0.1.0
 
 $ curl -H "Accept: application/json" "http://192.168.1.101/version"
 {"version": "v0.1.0"}
 
    
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/assets/www/request.html b/dist/pyrobusta/assets/www/request.html
index 7aed513..21f7aa2 100644
--- a/dist/pyrobusta/assets/www/request.html
+++ b/dist/pyrobusta/assets/www/request.html
@@ -101,9 +101,8 @@ 
    Streamed Requests
    
 request chunks are processed individually by calling registered route handlers
 for each chunk received. As a result, the application must process the request body
 incrementally rather than assuming the full payload is available at once.
    
-
    import pyrobusta.server.http_server as http_server
+
    from pyrobusta import application
 from pyrobusta.protocol.http import HttpEngine
-from pyrobusta.utils.helpers import normalize_path
 
 @HttpEngine.route("/app/chunks", "POST")
 def upload_chunks(http_ctx, payload: bytes):
@@ -116,7 +115,7 @@ 
    Streamed Requests
    
 
     if payload:
         # Wait for more chunks before setting response status
-        with open(normalize_path("/tmp/chunks.txt"), "ab") as f:
+        with open("/tmp/chunks.txt", "ab") as f:
             f.write(payload)
         return
 
@@ -125,8 +124,7 @@ 
    Streamed Requests
    
     return "text/plain", "OK"
 
 async def main():
-    server = http_server.HttpServer()
-    await server.start_socket_server()
+    await application.run()
     while True:
         await asyncio.sleep(1)
 
    
@@ -137,8 +135,8 @@ 
    Multipart Requests
    
 Unlike regular request bodies, multipart parts are parsed by the server before being passed
 to the application. Preprocessed parts consist of headers (dictionary) and the raw part body
 (bytes), passed as a tuple.
    
-
    Multipart state tracking
-The HTTP context exposes the boolean attributes
+
    Multipart State Tracking
    
+
    The HTTP context exposes the boolean attributes
 mp_is_first and
 mp_is_last
 to identify the first and final part of a multipart request. This allows the handler to maintain per-request
@@ -151,9 +149,8 @@ 
    Multipart Requests
    
 import asyncio
 from os import listdir, remove, rename, mkdir
 
-import pyrobusta.server.http_server as http_server
+from pyrobusta import application
 from pyrobusta.protocol.http import HttpEngine
-from pyrobusta.utils.helpers import normalize_path
 
 @HttpEngine.route("/app/parts", "POST")
 def handle_parts(http_ctx, payload: tuple):
@@ -163,8 +160,8 @@ 
    Multipart Requests
    
 
     _part_headers, part_body = payload
 
-    tmp_path = normalize_path(f"/tmp/parts.{http_ctx.id}.txt")
-    target_path = normalize_path(f"/www/user_data/parts.{http_ctx.id}.txt")
+    tmp_path = f"/tmp/parts.{http_ctx.id}.txt"
+    target_path = f"/www/user_data/parts.{http_ctx.id}.txt"
 
     with open(tmp_path, "ab") as f:
         f.write(part_body)
@@ -176,14 +173,13 @@ 
    Multipart Requests
    
         return "text/plain", "OK"
 
 async def main():
-    mkdir(normalize_path("/tmp"))
-    server = http_server.HttpServer()
-    await server.start_socket_server()
+    mkdir("/tmp")
+    await application.run()
     while True:
         await asyncio.sleep(1)
 
    
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/assets/www/response.html b/dist/pyrobusta/assets/www/response.html
index 42f3be9..883ea2b 100644
--- a/dist/pyrobusta/assets/www/response.html
+++ b/dist/pyrobusta/assets/www/response.html
@@ -47,6 +47,73 @@ 
    Status Codes
    
     http_ctx.terminate(404)
     return "text/plain", "Resource not found"
 
    
+
    The following list of status codes are supported by PyRobusta:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    Status CodeHTTP Status
    200OK
    201Created
    204No Content
    400Bad Request
    401Unauthorized
    403Forbidden
    404Not Found
    405Method Not Allowed
    408Request Timeout
    413Content Too Large
    415Unsupported Media Type
    500Internal Server Error
    503Service Unavailable
    505Version Not Supported
    
 
    Response Headers
    
 
    Response headers and response bodies can be configured through methods exposed by the HTTP context
 (set_response_header(), set_response_body()).
@@ -108,7 +175,7 @@ 
    Streamed Responses
    
 
    # /app.py
 import asyncio
 
-from pyrobusta.server import http_server
+from pyrobusta import application
 from pyrobusta.protocol.http import HttpEngine
 
 @HttpEngine.route("/stream", "GET")
@@ -133,8 +200,7 @@ 
    Streamed Responses
    
     http_ctx.resp_handler = generate_chunks
 
 async def main():
-    server = http_server.HttpServer()
-    await server.start_socket_server()
+    await application.run()
     while True:
         await asyncio.sleep(1)
 
    
@@ -164,7 +230,7 @@ 
    Streamed Multipart Responses
    
 
    # /app.py
 import asyncio
 
-from pyrobusta.server import http_server
+from pyrobusta import application
 from pyrobusta.protocol.http import HttpEngine
 
 def multipart_response(num_responses, part_size):
@@ -185,8 +251,7 @@ 
    Streamed Multipart Responses
    
     return "multipart/form-data", multipart_response(part_count, part_size)
 
 async def main():
-    server = http_server.HttpServer()
-    await server.start_socket_server()
+    await application.run()
     while True:
         await asyncio.sleep(1)
 
    
@@ -207,7 +272,7 @@ 
    Streamed Multipart Responses
    
 --pyrobusta-boundary--
 
    
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/assets/www/routing.html b/dist/pyrobusta/assets/www/routing.html
index 8d8e415..dd5673f 100644
--- a/dist/pyrobusta/assets/www/routing.html
+++ b/dist/pyrobusta/assets/www/routing.html
@@ -130,7 +130,7 @@ 
    Route Registration & Deregistrati
     return "text/plain", "OK"
 
    
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/assets/www/security.html b/dist/pyrobusta/assets/www/security.html
new file mode 100644
index 0000000..b665e88
--- /dev/null
+++ b/dist/pyrobusta/assets/www/security.html
@@ -0,0 +1,499 @@
+
+
+
+
+
+
+
+
+
    Authentication & Security
    
+
    ← Back
    
+
    This page documents the security features provided by PyRobusta,
+including HTTP Basic Authentication, role-based authorization, and TLS.
    
+
    Note: Authentication verifies the client's identity. Authorization determines
+whether the authenticated user is permitted to access a resource.
    
+
    
+
    Table of Contents
    
+
+
    
+
    Basic Authentication
    
+
    PyRobusta supports HTTP Basic Authentication with per-user credentials
+stored on the device. Passwords are stored as PBKDF2-HMAC-SHA256 hashes
+along with randomly generated salt values. Basic authentication is
+disabled by default. It can be enabled by setting
+http_auth=basic in pyrobusta.env.
    
+
    During initialization, PyRobusta reads pyrobusta.passwd by default
+from the server's working directory. Each entry specifies a username,
+one or more access role names, password hash and other related metadata.
+Set passwd_file in the configuration to specify an alternative user
+credentials file to load. For more information, see Server Configuration.
    
+
    PyRobusta defines a single realm (realm="Device") to authenticate against.
+The server response includes the WWW-Authenticate: Basic realm="Device" header
+when a request does not contain valid credentials.
    
+
    pyrobusta.passwd
    
+
    pyrobusta.passwd utilizes a passwd-like format, specifying one user per line,
+with each element of the user data separated by :. The expected format
+of a user entry is:
    
+
    <username>:<roles>:<password-hash>:<salt>:<iterations>:<algorithm>:<version>
+
    
+
      
+
    • username: name of the user (case insensitive)
      • 
+
    • roles: comma-separated role names (case insensitive)
      • 
+
    • password-hash: Base64-encoded PBKDF2 output
      • 
+
    • salt: Base64-encoded random salt
      • 
+
    • iterations: number of PBKDF2 iterations
      • 
+
    • algorithm: password hashing algorithm (currently PBKDF2-HMAC-SHA256)
      • 
+
    • version: version of PyRobusta when the user was created
      • 
+
    
+
    # Example
+# File: /pyrobusta.passwd
+szeka9:api_admin:JlSousyaBB87FIIS/xoQIWTCH7+Z/yjQao5NGE7O/ww=:Zz1n+l9UN89hKlpnnvcXAg==:5000:PBKDF2-HMAC-SHA256:v0.8.0
+alice:api_user,app_viewer:mKmmf5wBEtlkty7LEcphieciOd3Pl0yY7r3WmDiZnzg=:XTQgg3Has79lDTNYVW+aPw==:5000:PBKDF2-HMAC-SHA256:v0.8.0
+bob:api_user,app_maintainer:sOqLqi48jCQUiR+VpcCcfMgKcKCspbE902y0yFe0DV4=:5PzMbQQJtQRP8aZ9C7t8qQ==:5000:PBKDF2-HMAC-SHA256:v0.8.0
+[...]
+
    
+
    New users can be added programmatically through the IAM API:
    
+
    from pyrobusta.utils.iam import IAMDatabase
+iam_db = IAMDatabase("pyrobusta.passwd", "pyrobusta.roles")
+iam_db.load()
+iam_db.create_user("john", "john's-secret-password", ["role-1", "role-2"])
+
    
+
    Password verification uses PBKDF2-HMAC-SHA256 with a default iteration count of 5000.
+The iteration count is intentionally chosen as a compromise between resistance against
+offline attacks and the computational limitations of microcontroller-class hardware.
+Because lower iteration counts reduce the computational cost of each password guess,
+PyRobusta enforces strong password requirements to increase the password search
+space and improve resistance against brute-force attacks.
    
+
    iam_db.create_user("john", "secret", ["role-1", "role-2"])
+Traceback (most recent call last):
+  File "<stdin>", line 1, in <module>
+  File "src/pyrobusta/utils/iam.py", line 198, in create_user
+  File "src/pyrobusta/utils/crypto.py", line 125, in validate_password
+ValueError: Password must be at least 16 characters
+
    
+
    HTTP Sessions
    
+
    Without session authentication, each HTTP request authenticated with Basic Auth requires a
+new password verification operation. Since PBKDF2 is intentionally computationally expensive,
+this can introduce noticeable latency on microcontroller-class hardware.
    
+
    To avoid repeated password verification, PyRobusta can issue stateless session cookies
+after a successful authentication. Subsequent requests are authenticated using the session
+cookie instead of recomputing the PBKDF2 password hash.
    
+
    Session cookies are cryptographically signed and validated by the server without maintaining
+per-session state. Session signing keys are derived from per-user secrets that are randomly
+generated during server startup and stored only in memory. Consequently, all existing
+sessions are invalidated automatically when the server restarts.
    
+
    Stateless sessions are enabled by setting http_sessions=true in pyrobusta.env.
+Sessions expire after 15 minutes by default. The session lifetime can be configured with
+http_session_ttl_sec.
    
+
    Authorization
    
+
    When HTTP Basic Authentication is enabled, PyRobusta provides role-based access control (RBAC).
+Resource permissions are determined by the authenticated user's assigned roles.
+Each user can be assigned one or more roles, configured in pyrobusta.passwd.
    
+
    While pyrobusta.passwd assigns roles to users, pyrobusta.roles maps those roles to
+HTTP methods and server resources. Authorization follows a least-privilege model.
+Users have no permissions unless explicitly granted by one or more authorization rules.
+Each matching rule grants additional permissions. Requests that do not match an authorization
+rule receive HTTP 403 Forbidden.
    
+
    Set roles_file in the configuration to specify an alternative role configuration file to load.
+For more information, see Server Configuration.
    
+
    pyrobusta.roles
    
+
    pyrobusta.roles consists of one or more authorization blocks. Each block defines one or
+more path patterns, followed by one or more authorization rules. Every authorization rule
+applies to every path pattern declared within the same block.
    
+
    <path-pattern>
+<path-pattern>
+...
+    <HTTP-method>: <role>,<role>,...
+    <HTTP-method>: <role>,<role>,...
+    ...
+
+<path-pattern>
+    ...
+
    
+
    Authorization rules are selected based on pattern specificity rather than their
+order in pyrobusta.roles. Path patterns support the following forms, ordered
+from least to most specific. Each request is matched against the most specific
+pattern, and only the roles associated with the selected pattern are considered
+during authorization.
    
+
    /**                        # Match any path
+/*                         # Match direct children of /
+/app                       # Exact match
+/app/**                    # Match any descendant of /app
+/app/*                     # Match direct children of /app
+/app/*/resources           # Match a single wildcard segment
+/app/endpoint/resources    # Exact match
+
    
+
    Note: recursive globs (**) are only supported as the final path segment.
+Allowing ** in intermediate segments would introduce ambiguous matches
+and is therefore not supported.
    
+
    # File: /pyrobusta.roles
+
+# ---------------------------------------------------------
+# Example: public resources (/, /index.html, /styles.css, ...)
+/
+/*
+    GET,HEAD: *
+
+# ---------------------------------------------------------
+# Example: apply rule to parent and child resources
+/app/resource
+/app/resource/*
+    GET: resource_viewer
+    POST,PUT,DELETE: resource_maintainer
+
+# ---------------------------------------------------------
+# Example: apply rule to paths of any length with **
+/app/api/**
+    GET: api_viewer
+    POST,PUT,DELETE: api_maintainer
+
+# ---------------------------------------------------------
+# Example: require api_admin access for all HTTP methods
+/app/api/management
+    *: api_admin
+
+# ---------------------------------------------------------
+# Example: restrict all access to a resource
+/app/secret
+    *:
+
+# ---------------------------------------------------------
+# Example: assign multiple roles
+/app/logs
+    GET: api_admin,api_maintainer
+
    
+
    Note: The special role * grants public access regardless of the authenticated user's roles.
+Rules that specify * do not require authentication.
    
+
    CSRF Protection
    
+
    Credentials used with HTTP Basic Authentication may be automatically attached to requests by a browser.
+This makes HTTP Basic Authentication vulnerable to CSRF (Cross-Site Request Forgery) attacks,
+allowing an attacker-controlled website to cause the browser to issue requests to the server on
+behalf of an authenticated user.
    
+
    To prevent CSRF attacks, PyRobusta applies the Signed Double-Submit Cookie pattern. For unsafe HTTP methods
+(POST, PUT, PATCH, and DELETE), the client must return the CSRF token received from the server as
+a cookie. The client must send the same token in the X-CSRF-Token request header. The server
+rejects requests where the cookie value and header value do not match.
    
+
    A malicious website cannot read the CSRF cookie from another origin because of the browser's
+same-origin policy. Therefore, a malicious website cannot provide a valid CSRF token in the request header.
+Cryptographic signing prevents attackers from forging valid CSRF tokens without knowledge of the server-side secret.
    
+
    PyRobusta generates CSRF tokens using HMAC-SHA256 with per-user secrets generated during server
+initialization. User secrets exist only in memory, so restarting the server invalidates all
+previous CSRF tokens. The server issues a CSRF cookie after successful authentication. Clients
+must include the same token in the X-CSRF-Token header for subsequent unsafe requests.
    
+
    Tokens generated by PyRobusta have the following format:
    
+
    <hex-encoded-random-nonce>.<hex-encoded-HMAC-SHA256-signature>
+
    
+
    During verification, PyRobusta recalculates the HMAC-SHA256 signature over the nonce using the
+user secret and compares it with the signature provided in the token. Requests are rejected with HTTP
+403 Forbidden if the token signature is invalid or if the cookie and X-CSRF-Token header values do not match.
    
+
    Authentication & Authorization Flow
    
+
    Public
    Protected
    Yes
    No
    Yes
    No
    No
    Yes
    No
    Yes
    No
    Yes
    No
    Yes
    Yes
    No
    Incoming request
    Resolve resource
    Resource security policy
    Process request
    Read cookie data
    Session cookie?
    Validate session
    Use configured auth method
    Session valid?
    Authenticated identity
    Authorization header?
    401 Unauthorized
    Validate credentials
    Credentials valid?
    CSRF required?
    Authorize
    CSRF token valid?
    403 Forbidden
    Permission granted?
    
+
    PyRobusta returns the following HTTP status codes for authentication and authorization failures:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ConditionResponse
    Missing authentication credentials401 Unauthorized
    Invalid authentication credentials401 Unauthorized
    Authenticated, but CSRF validation failed403 Forbidden
    Authenticated, but authorization failed403 Forbidden
    
+
    Content Serving & Browser Security Headers
    
+
    Unsafe Content Types
    
+
    To lower the risk of cross-site scripting (XSS) attacks, browser-interpreted or
+active content types like text/html and application/javascript are served
+as attachments by setting Content-Disposition: attachment. This rule applies
+to every file stored under /www/user_data. The following file extensions are
+allowlisted and are served inline with their corresponding content types:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ExtensionContent-Type header
    .csvtext/csv
    .gifimage/gif
    .icoimage/x-icon
    .jpeg/.jpgimage/jpeg
    .jsonapplication/json
    .logtext/plain
    .pngimage/png
    .txttext/plain
    .webpimage/webp
    
+
    Unless overridden by the application, responses include X-Content-Type-Options: nosniff
+to prevent browsers from interpreting content using a different MIME type than the one
+provided by the server.
    
+
    Browser Security Headers
    
+
    Content Security Policy
    
+
    Content Security Policy controls which resources the browser is allowed to
+load, execute, and embed, acting as a defense mechanism against XSS
+(cross-site scripting) vulnerabilities. PyRobusta includes a default
+Content-Security-Policy header in every response. Applications may override
+this header when required, but doing so can reduce browser-side security
+protections.
    
+
    The following defaults are applicable to the Content-Security-Policy header:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    PolicySettingMeaning
    default-src'self'Resources are only allowed from the same origin by default.
    script-src'self'JavaScript may only be loaded from the same origin. Inline scripts are blocked.
    style-src'self' 'unsafe-inline'Stylesheets may be loaded from the same origin. Inline styles are allowed.
    object-src'none'Embedded plugin content such as <object> and <embed> is disabled.
    base-uri'self'The document base URL can only be set to the same origin.
    frame-ancestors'none'Prevents the application from being embedded in frames.
    
+
    Inline styles are permitted for compatibility with embedded resources such as
+SVG files. Inline JavaScript remains disabled by the default policy.
    
+
    Referrer Policy
    
+
    Referrer Policy controls the amount of referrer information sent by the browser.
+The following default is applicable to the Referrer-Policy header:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    HeaderSettingMeaning
    Referrer-Policyno-referrerPrevents browsers from sending the originating URL in the Referer header.
    
+
    HTTPS / TLS
    
+
    TLS is enabled by the tls configuration parameter in pyrobusta.env. When enabled, the certificate and private
+key specified by the tls_cert_file and tls_key_file configuration are loaded. The underlying asyncio server
+accepts a configured MicroPython ssl.SSLContext through the ssl parameter of asyncio.start_server().
    
+
    TLS capabilities, including supported certificate and private-key formats, key types, cipher suites, and cryptographic
+algorithms, depend on the SSL implementation and configuration provided by the target MicroPython port. The configurations
+documented here are those supported and tested for PyRobusta on the ESP32 port. Larger RSA key sizes and larger elliptic
+curves require additional RAM and computational resources during TLS initialization and connection handling.
+The recommended configurations provide a balance between compatibility, security, and resource usage.
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    AlgorithmSize/curveKey/Certificate formatComment
    ECDSAP-256DERRecommended ECDSA configuration
    ECDSAP-384DER
    ECDSAP-256PEM
    RSA2048DERRecommended RSA configuration
    RSA3072DER
    RSA4096DER
    RSA2048PEM
    
+
    Certificate Creation & Installation
    
+
    The following section provides examples for certificate creation.
+The examples below use ECDSA P-256, which is the recommended configuration.
+RSA certificates can be generated similarly by replacing the EC key-generation commands
+with RSA key generation.
    
+
    Replace device.local with the hostname used to access the device, as well as
+the certificate subject (subjectAltName) values according to your deployment.
+If the device is accessed by IP address, use an IP SAN instead, for
+example subjectAltName=IP:192.168.1.101.
    
+
    Self-signed Certificate
    
+
    # Create private key for the server
+openssl genpkey -algorithm EC \
+  -pkeyopt ec_paramgen_curve:P-256 \
+  -outform DER -out key.der
+
+# Create certificate for the server, signed by itself
+openssl req -x509 -new \
+  -key key.der -keyform DER \
+  -out cert.der -outform DER \
+  -days 365 \
+  -subj /CN=device.local \
+  -addext 'basicConstraints=critical,CA:FALSE' \
+  -addext 'keyUsage=critical,digitalSignature' \
+  -addext 'subjectAltName=DNS:device.local'
+
    
+
    The above commands produce:
    
+
    key.der          ECDSA P-256 private key
+cert.der         self-signed certificate
+
    
+
    CA-signed Certificate
    
+
    # Optional: generate CA private key and certificate if does not exist
+openssl genpkey -algorithm EC \
+  -pkeyopt ec_paramgen_curve:P-256 \
+  -outform DER -out ca.key.der
+
+openssl req -new -x509 \
+  -key ca.key.der -keyform DER \
+  -out ca.crt.der -outform DER \
+  -days 3650 -subj /CN=TestCA \
+  -addext 'basicConstraints=critical,CA:TRUE' \
+  -addext 'keyUsage=critical,keyCertSign,cRLSign'
+
+# Create server private key certificate signing request (CSR)
+openssl genpkey -algorithm EC \
+  -pkeyopt ec_paramgen_curve:P-256 \
+  -outform DER -out key.der
+
+openssl req -new \
+  -key key.der -keyform DER \
+  -out server.csr \
+  -subj /CN=device.local
+
+# Create certificate for the server, signed by the CA
+openssl x509 -req \
+  -in server.csr \
+  -CA ca.crt.der -CAform DER \
+  -CAkey ca.key.der -CAkeyform DER \
+  -CAcreateserial \
+  -out cert.der -outform DER \
+  -days 365 \
+  -extfile <(printf '%s\n' \
+    'basicConstraints=critical,CA:FALSE' \
+    'keyUsage=critical,digitalSignature' \
+    'subjectAltName=DNS:device.local')
+
    
+
    The above commands produce:
    
+
    ca.key.der       CA private key
+ca.crt.der       CA certificate
+server.csr       Server CSR
+key.der          Server private key
+cert.der         CA-signed server certificate
+
    
+
    Install certificates into the root directory with mpremote:
    
+
    $ mpremote connect /dev/ttyACM1 soft-reset
+$ mpremote connect /dev/ttyACM1 cp key.der :/key.der
+$ mpremote connect /dev/ttyACM1 cp cert.der :/cert.der
+
    
+
    
+
    PyRobusta v0.9.0 Web Server
    
+
+
+
diff --git a/dist/pyrobusta/assets/www/static_content.html b/dist/pyrobusta/assets/www/static_content.html
index 801e137..2b22f49 100644
--- a/dist/pyrobusta/assets/www/static_content.html
+++ b/dist/pyrobusta/assets/www/static_content.html
@@ -60,12 +60,28 @@ 
    MIME Type Handling
    
 
 
 
+.css
+text/css
+
+
+.csv
+text/csv
+
+
+.gif
+image/gif
+
+
 .html
 text/html
 
 
-.css
-text/css
+.ico
+image/x-icon
+
+
+.jpeg/.jpg
+image/jpeg
 
 
 .js
@@ -76,37 +92,37 @@ 
    MIME Type Handling
    
 application/json
 
 
-.ico
-image/x-icon
+.log
+text/plain
 
 
-.jpeg
-image/jpeg
+.png
+image/png
 
 
-.jpg
-image/jpeg
+.raw
+application/octet-stream
 
 
-.png
-image/png
+.svg
+image/svg+xml
 
 
 .txt
 text/plain
 
 
-.gif
-image/gif
+.webp
+image/webp
 
 
-.raw, unknown extensions
+unknown extensions
 application/octet-stream
 
 
 
 
    
-
    PyRobusta v0.8.0 Web Server
    
+
    PyRobusta v0.9.0 Web Server
    
 
 
 
diff --git a/dist/pyrobusta/bindings/http_connection.mpy b/dist/pyrobusta/bindings/http_connection.mpy
index 8d77afb..0b757c5 100644
Binary files a/dist/pyrobusta/bindings/http_connection.mpy and b/dist/pyrobusta/bindings/http_connection.mpy differ
diff --git a/dist/pyrobusta/connectivity/__init__.py b/dist/pyrobusta/connectivity/__init__.py
deleted file mode 100644
index e69de29..0000000
diff --git a/dist/pyrobusta/connectivity/wifi.mpy b/dist/pyrobusta/connectivity/wifi.mpy
deleted file mode 100644
index d89dfb2..0000000
Binary files a/dist/pyrobusta/connectivity/wifi.mpy and /dev/null differ
diff --git a/dist/pyrobusta/protocol/__init__.py b/dist/pyrobusta/protocol/__init__.py
index e69de29..ad06e05 100644
--- a/dist/pyrobusta/protocol/__init__.py
+++ b/dist/pyrobusta/protocol/__init__.py
@@ -0,0 +1,21 @@
+"""
+Common exceptions
+"""
+
+
+class InvalidHeaders(ValueError):
+    """Exception for invalid HTTP/MIME headers."""
+
+    pass
+
+
+class InvalidContentLength(ValueError):
+    """Exception for content-length related erros."""
+
+    pass
+
+
+class MalformedRequest(ValueError):
+    """Exception for malformed requests."""
+
+    pass
diff --git a/dist/pyrobusta/protocol/http.mpy b/dist/pyrobusta/protocol/http.mpy
index 5879026..ab9c054 100644
Binary files a/dist/pyrobusta/protocol/http.mpy and b/dist/pyrobusta/protocol/http.mpy differ
diff --git a/dist/pyrobusta/protocol/http_basic_auth.mpy b/dist/pyrobusta/protocol/http_basic_auth.mpy
new file mode 100644
index 0000000..c7a1976
Binary files /dev/null and b/dist/pyrobusta/protocol/http_basic_auth.mpy differ
diff --git a/dist/pyrobusta/protocol/http_cookie.mpy b/dist/pyrobusta/protocol/http_cookie.mpy
new file mode 100644
index 0000000..c2d4b0f
Binary files /dev/null and b/dist/pyrobusta/protocol/http_cookie.mpy differ
diff --git a/dist/pyrobusta/protocol/http_file_server.mpy b/dist/pyrobusta/protocol/http_file_server.mpy
index 1c30f91..f039915 100644
Binary files a/dist/pyrobusta/protocol/http_file_server.mpy and b/dist/pyrobusta/protocol/http_file_server.mpy differ
diff --git a/dist/pyrobusta/protocol/http_multipart.mpy b/dist/pyrobusta/protocol/http_multipart.mpy
index d5ad156..e8d17a5 100644
Binary files a/dist/pyrobusta/protocol/http_multipart.mpy and b/dist/pyrobusta/protocol/http_multipart.mpy differ
diff --git a/dist/pyrobusta/protocol/http_security.mpy b/dist/pyrobusta/protocol/http_security.mpy
new file mode 100644
index 0000000..4a537f6
Binary files /dev/null and b/dist/pyrobusta/protocol/http_security.mpy differ
diff --git a/dist/pyrobusta/server/http_server.mpy b/dist/pyrobusta/server/http_server.mpy
index 542660d..503461f 100644
Binary files a/dist/pyrobusta/server/http_server.mpy and b/dist/pyrobusta/server/http_server.mpy differ
diff --git a/dist/pyrobusta/stream/buffer.mpy b/dist/pyrobusta/stream/buffer.mpy
index 4b3da96..11e573f 100644
Binary files a/dist/pyrobusta/stream/buffer.mpy and b/dist/pyrobusta/stream/buffer.mpy differ
diff --git a/dist/pyrobusta/transport/connection.mpy b/dist/pyrobusta/transport/connection.mpy
index e74282a..827ee32 100644
Binary files a/dist/pyrobusta/transport/connection.mpy and b/dist/pyrobusta/transport/connection.mpy differ
diff --git a/dist/pyrobusta/utils/assets.mpy b/dist/pyrobusta/utils/assets.mpy
index 7093beb..1b41479 100644
Binary files a/dist/pyrobusta/utils/assets.mpy and b/dist/pyrobusta/utils/assets.mpy differ
diff --git a/dist/pyrobusta/utils/config.mpy b/dist/pyrobusta/utils/config.mpy
index cf1ccad..7f68b03 100644
Binary files a/dist/pyrobusta/utils/config.mpy and b/dist/pyrobusta/utils/config.mpy differ
diff --git a/dist/pyrobusta/utils/crypto.mpy b/dist/pyrobusta/utils/crypto.mpy
new file mode 100644
index 0000000..c52dd7f
Binary files /dev/null and b/dist/pyrobusta/utils/crypto.mpy differ
diff --git a/dist/pyrobusta/utils/helpers.mpy b/dist/pyrobusta/utils/helpers.mpy
deleted file mode 100644
index 38a8103..0000000
Binary files a/dist/pyrobusta/utils/helpers.mpy and /dev/null differ
diff --git a/dist/pyrobusta/utils/iam.mpy b/dist/pyrobusta/utils/iam.mpy
new file mode 100644
index 0000000..16d199d
Binary files /dev/null and b/dist/pyrobusta/utils/iam.mpy differ
diff --git a/dist/pyrobusta/utils/lexpath.mpy b/dist/pyrobusta/utils/lexpath.mpy
new file mode 100644
index 0000000..be39b0e
Binary files /dev/null and b/dist/pyrobusta/utils/lexpath.mpy differ
diff --git a/dist/pyrobusta/utils/logging.mpy b/dist/pyrobusta/utils/logging.mpy
index e57bf26..dd8a318 100644
Binary files a/dist/pyrobusta/utils/logging.mpy and b/dist/pyrobusta/utils/logging.mpy differ
diff --git a/dist/pyrobusta/utils/patch.mpy b/dist/pyrobusta/utils/patch.mpy
index ccb4f2d..5c28661 100644
Binary files a/dist/pyrobusta/utils/patch.mpy and b/dist/pyrobusta/utils/patch.mpy differ
diff --git a/docs/application_development/concepts.md b/docs/application_development/concepts.md
index a8cacd7..f55d310 100644
--- a/docs/application_development/concepts.md
+++ b/docs/application_development/concepts.md
@@ -149,4 +149,4 @@ incremental request processing, and deterministic behavior suitable for resource
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/configuration.md b/docs/application_development/configuration.md
index e6737be..c045598 100644
--- a/docs/application_development/configuration.md
+++ b/docs/application_development/configuration.md
@@ -95,4 +95,4 @@ and configuration-loading functionality.
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/error_handling.md b/docs/application_development/error_handling.md
index f8d7217..01b546a 100644
--- a/docs/application_development/error_handling.md
+++ b/docs/application_development/error_handling.md
@@ -118,4 +118,4 @@ def handler(http_ctx, _):
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/file_server.md b/docs/application_development/file_server.md
index b605dc2..ff5484e 100644
--- a/docs/application_development/file_server.md
+++ b/docs/application_development/file_server.md
@@ -136,4 +136,4 @@ $ curl -X DELETE \
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/index.md b/docs/application_development/index.md
index 2f5db58..dd12fba 100644
--- a/docs/application_development/index.md
+++ b/docs/application_development/index.md
@@ -23,4 +23,4 @@ Then continue with the remaining guides in the order listed below.
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/introduction.md b/docs/application_development/introduction.md
index 6784293..111cc29 100644
--- a/docs/application_development/introduction.md
+++ b/docs/application_development/introduction.md
@@ -95,4 +95,4 @@ $ curl -H "Accept: application/json" "http://192.168.1.101/version"
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/performance.md b/docs/application_development/performance.md
index 9439173..2c5d1e1 100644
--- a/docs/application_development/performance.md
+++ b/docs/application_development/performance.md
@@ -23,4 +23,4 @@ This page is work in progress. Refer to the [main page](index.md) for available
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/reference.md b/docs/application_development/reference.md
index b934d48..1c8dcf5 100644
--- a/docs/application_development/reference.md
+++ b/docs/application_development/reference.md
@@ -26,4 +26,4 @@ This page is work in progress. Refer to the [main page](index.md) for available
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/request.md b/docs/application_development/request.md
index 5832b48..83306e3 100644
--- a/docs/application_development/request.md
+++ b/docs/application_development/request.md
@@ -202,4 +202,4 @@ async def main():
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/response.md b/docs/application_development/response.md
index ec91e1e..a9f0c6e 100644
--- a/docs/application_development/response.md
+++ b/docs/application_development/response.md
@@ -248,4 +248,4 @@ XXXXXXXXXX
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/routing.md b/docs/application_development/routing.md
index 3c9ec18..8a1c9fb 100644
--- a/docs/application_development/routing.md
+++ b/docs/application_development/routing.md
@@ -148,4 +148,4 @@ def enable_sensor(http_ctx, enabled):
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/security.md b/docs/application_development/security.md
index ff6390d..2429aaa 100644
--- a/docs/application_development/security.md
+++ b/docs/application_development/security.md
@@ -468,4 +468,4 @@ $ mpremote connect /dev/ttyACM1 cp cert.der :/cert.der
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/server_lifecycle.md b/docs/application_development/server_lifecycle.md
index 7ec47c3..9cf47d9 100644
--- a/docs/application_development/server_lifecycle.md
+++ b/docs/application_development/server_lifecycle.md
@@ -26,4 +26,4 @@ This page is work in progress. Refer to the [main page](index.md) for available
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/docs/application_development/static_content.md b/docs/application_development/static_content.md
index 7147103..0f57980 100644
--- a/docs/application_development/static_content.md
+++ b/docs/application_development/static_content.md
@@ -76,4 +76,4 @@ The following mapping between extensions and content types is maintained by the
 
 ---
 
-PyRobusta v0.8.0 Web Server
+PyRobusta v0.9.0 Web Server
diff --git a/package.json b/package.json
index 09a56af..1ee75e8 100644
--- a/package.json
+++ b/package.json
@@ -1,13 +1,9 @@
 {
-  "version": "v0.8.0",
+  "version": "v0.9.0",
   "urls": [
     [
-      "pyrobusta/connectivity/wifi.mpy",
-      "github:szeka9/PyRobusta/dist/pyrobusta/connectivity/wifi.mpy"
-    ],
-    [
-      "pyrobusta/connectivity/__init__.py",
-      "github:szeka9/PyRobusta/dist/pyrobusta/connectivity/__init__.py"
+      "pyrobusta/application.mpy",
+      "github:szeka9/PyRobusta/dist/pyrobusta/application.mpy"
     ],
     [
       "pyrobusta/transport/__init__.py",
@@ -25,6 +21,10 @@
       "pyrobusta/assets/www/request.html",
       "github:szeka9/PyRobusta/dist/pyrobusta/assets/www/request.html"
     ],
+    [
+      "pyrobusta/assets/www/error_handling.html",
+      "github:szeka9/PyRobusta/dist/pyrobusta/assets/www/error_handling.html"
+    ],
     [
       "pyrobusta/assets/www/index.html",
       "github:szeka9/PyRobusta/dist/pyrobusta/assets/www/index.html"
@@ -37,6 +37,10 @@
       "pyrobusta/assets/www/file_server.html",
       "github:szeka9/PyRobusta/dist/pyrobusta/assets/www/file_server.html"
     ],
+    [
+      "pyrobusta/assets/www/security.html",
+      "github:szeka9/PyRobusta/dist/pyrobusta/assets/www/security.html"
+    ],
     [
       "pyrobusta/assets/www/introduction.html",
       "github:szeka9/PyRobusta/dist/pyrobusta/assets/www/introduction.html"
@@ -58,8 +62,12 @@
       "github:szeka9/PyRobusta/dist/pyrobusta/assets/www/response.html"
     ],
     [
-      "pyrobusta/utils/helpers.mpy",
-      "github:szeka9/PyRobusta/dist/pyrobusta/utils/helpers.mpy"
+      "pyrobusta/utils/lexpath.mpy",
+      "github:szeka9/PyRobusta/dist/pyrobusta/utils/lexpath.mpy"
+    ],
+    [
+      "pyrobusta/utils/crypto.mpy",
+      "github:szeka9/PyRobusta/dist/pyrobusta/utils/crypto.mpy"
     ],
     [
       "pyrobusta/utils/__init__.py",
@@ -81,6 +89,10 @@
       "pyrobusta/utils/assets.mpy",
       "github:szeka9/PyRobusta/dist/pyrobusta/utils/assets.mpy"
     ],
+    [
+      "pyrobusta/utils/iam.mpy",
+      "github:szeka9/PyRobusta/dist/pyrobusta/utils/iam.mpy"
+    ],
     [
       "pyrobusta/protocol/http_multipart.mpy",
       "github:szeka9/PyRobusta/dist/pyrobusta/protocol/http_multipart.mpy"
@@ -93,10 +105,22 @@
       "pyrobusta/protocol/__init__.py",
       "github:szeka9/PyRobusta/dist/pyrobusta/protocol/__init__.py"
     ],
+    [
+      "pyrobusta/protocol/http_basic_auth.mpy",
+      "github:szeka9/PyRobusta/dist/pyrobusta/protocol/http_basic_auth.mpy"
+    ],
+    [
+      "pyrobusta/protocol/http_security.mpy",
+      "github:szeka9/PyRobusta/dist/pyrobusta/protocol/http_security.mpy"
+    ],
     [
       "pyrobusta/protocol/http_file_server.mpy",
       "github:szeka9/PyRobusta/dist/pyrobusta/protocol/http_file_server.mpy"
     ],
+    [
+      "pyrobusta/protocol/http_cookie.mpy",
+      "github:szeka9/PyRobusta/dist/pyrobusta/protocol/http_cookie.mpy"
+    ],
     [
       "pyrobusta/stream/__init__.py",
       "github:szeka9/PyRobusta/dist/pyrobusta/stream/__init__.py"
diff --git a/src/pyrobusta/__init__.py b/src/pyrobusta/__init__.py
index f47476b..a82c93f 100644
--- a/src/pyrobusta/__init__.py
+++ b/src/pyrobusta/__init__.py
@@ -2,5 +2,5 @@
 
 from os import getcwd
 
-PYROBUSTA_VERSION = "v0.8.0"
+PYROBUSTA_VERSION = "v0.9.0"
 WORKING_DIR = getcwd().rstrip("/")