Packages

bandit

1.6.3
1.12.1 1.12.0 1.11.1 1.11.0 1.10.4 1.10.3 1.10.2 1.10.1 1.10.0 retired 1.9.0 1.8.0 1.7.0 1.6.11 1.6.10 1.6.9 1.6.8 1.6.7 1.6.6 1.6.5 1.6.4 1.6.3 1.6.2 1.6.1 1.6.0 1.5.7 1.5.6 1.5.5 1.5.4 1.5.3 1.5.2 1.5.1 1.5.0 1.4.2 1.4.1 1.4.0 1.3.0 1.2.3 1.2.2 1.2.1 1.2.0 1.1.3 1.1.2 1.1.1 1.1.0 1.0.0 1.0.0-pre.18 1.0.0-pre.17 1.0.0-pre.16 1.0.0-pre.15 1.0.0-pre.14 1.0.0-pre.13 1.0.0-pre.12 1.0.0-pre.11 1.0.0-pre.10 1.0.0-pre.9 1.0.0-pre.8 1.0.0-pre.7 1.0.0-pre.6 1.0.0-pre.5 1.0.0-pre.4 1.0.0-pre.3 1.0.0-pre.2 1.0.0-pre.1 0.7.7 0.7.6 0.7.5 0.7.4 0.7.3 0.7.2 0.7.1 0.7.0 0.6.11 0.6.10 0.6.9 0.6.8 0.6.7 0.6.6 0.6.5 0.6.4 0.6.3 0.6.2 0.6.1 0.6.0 0.5.11 0.5.10 0.5.9 0.5.8 0.5.7 0.5.6 0.5.5 0.5.4 0.5.3 0.5.2 0.5.1 0.5.0 0.4.10 0.4.9 0.4.8 0.4.7 0.4.6 0.4.5 0.4.4 0.4.3 0.4.2 0.4.1 0.4.0 0.3.9 0.3.8 0.3.7 0.3.6 0.3.5 0.3.4 0.3.3 0.3.2 0.2.3 0.2.2 0.2.1 0.2.0 0.1.1 0.1.0

A pure-Elixir HTTP server built for Plug & WebSock apps

Security advisory: This version has known vulnerabilities. View advisories
HexDocs

Current section

Files

Jump to
Readme
120 Versions
5 Dependencies
Dependants
8 Advisories
Files
Activity
bandit lib bandit http1 README.md
Raw

lib/bandit/http1/README.md 

# HTTP/1 Handler



Included in this folder is a complete `ThousandIsland.Handler` based implementation of HTTP/1.x as

defined in [RFC 9112](https://datatracker.ietf.org/doc/rfc9112).



## Process model



Within a Bandit server, an HTTP/1 connection is modeled as a single process.

This process is tied to the lifecycle of the underlying TCP connection; in the

case of an HTTP client which makes use of HTTP's keep-alive feature to make

multiple requests on the same connection, all of these requests will be serviced

by this same process.



The execution model to handle a given request is quite straightforward: the

underlying [Thousand Island](https://github.com/mtrudel/thousand_island) library

will call `Bandit.HTTP1.Handler.handle_data/3`, which will then construct a

`Bandit.HTTP1.Socket` struct that conforms to the `Bandit.HTTPTransport`

protocol. It will then call `Bandit.Pipeline.run/3`, which will go through the

process of reading the request (by calling functions on the

`Bandit.HTTPTransport` protocol), and constructing a `Plug.Conn` structure to

represent the request and subsequently pass it to the configured `Plug` module.



# Testing



All of this is exhaustively tested. Tests are located in `request_test.exs`, and

are broadly either concerned with testing network-facing aspects of the

implementation (ie: how well Bandit satisfies the relevant RFCs) or the Plug-facing

aspects of the implementation.



Unfortunately, there is no HTTP/1 equivalent to the external h2spec test suite.