Module origin 

The HTTP origin: what the browser actually talks to.

The daemon answers two shapes of request on one loopback listener. A proxied request arrives in absolute form because a PAC sent it here, and its Host is <alias>.<suffix>; that is the path which gives the page a real origin under the URL the user typed. A direct request arrives by address and exists so the daemon is usable without touching proxy settings at all.

Every request starts at the listing cache, not at the remote. One fresh listing of a parent directory answers four questions locally – does this name exist, is it a directory, is it a symlink, and is the copy the browser already holds still current – and only a body the cache does not hold costs a round trip.

Modules

guard

Request guards: two separate checks for two separate attacks.

mime

Extension to Content-Type.

pac

The PAC script that makes http://<alias>.<suffix>/ reach this daemon.

range

Range requests, and the two directions in which they are declined.

Structs

Alias

One alias, checked.

Bound

A listening socket and the origin that will answer on it.

Origin

Startup

What to tell the reader about a daemon that has just come up.

Enums

Named

Where an alias’s name came from, which is what failing to open it means.