Eyre Data Types
This document describes the data types used by Eyre as defined in /sys/lull.hoon. It's separated into two sections:
Eyre - Eyre-specific data types.
HTTP - HTTP data types shared between Eyre and Iris.
Eyre
$cache-entry
$cache-entry+$ cache-entry
$: auth=?
$= body
$% [%payload =simple-payload:http]
== ==auth: Whether the request must include a valid session cookie or otherwise be authenticated. If this is false, the entry will be publicly accessible.body: The HTTP response to give. This contains a[%payload =simple-payload:http]. See the$simple-payload:httpfor more details of the data.
$origin
$origin+$ origin @toriginA single CORS origin as used in an HTTP Origin header and the $cors-registry.
$cors-registry
$cors-registry+$ cors-registry
$: requests=(set origin)
approved=(set origin)
rejected=(set origin)
==CORS origins categorised by approval status. The requests set contains all $origins Eyre has received in the headers of HTTP requests that have not been explicitly approved or rejected. The approved and rejected sets are those that have been explicitly approved or rejected.
$outstanding-connection
$outstanding-connection+$ outstanding-connection
$: =action
=inbound-request
response-header=(unit response-header:http)
bytes-sent=@ud
==An HTTP connection that is currently open. The $action is how it's being handled (e.g. by a Gall app, the channel system, etc). The $inbound-request is the original request which opened the connection. The response-header contains the status code and headers. The bytes-sent is the total bytes sent so far in response.
$authentication-state
$authentication-state+$ authentication-state sessions=(map @uv session)This represents the authentication state of all sessions. It maps session cookies (without the urbauth-{SHIP}= prefix) to $sessions.
$session
$session+$ session
$: expiry-time=@da
channels=(set @t)
==This represents server-side data about a session. The expiry-time is when the session expires and channels is the set of $channel names opened by the session.
$channel-state
$channel-state+$ channel-state
$: session=(map @t channel)
duct-to-key=(map duct @t)
==The state used by the channel system. The session is a map between channel names and $channels and the duct-to-key maps ducts to channel names.
$timer
$timer+$ timer
$: date=@da
=duct
==A reference to a timer so it can be cancelled or updated. The date is when it will fire and the duct is what set the timer.
$channel-event
$channel-event+$ channel-event
$% $>(%poke-ack sign:agent:gall)
$>(%watch-ack sign:agent:gall)
$>(%kick sign:agent:gall)
[%fact =mark =noun]
==An unacknowledged event in the channel system.
$channel
$channel +$ channel
$: mode=?(%json %jam)
state=(each timer duct)
next-id=@ud
last-ack=@da
events=(qeu [id=@ud request-id=@ud =channel-event])
unacked=(map @ud @ud)
subscriptions=(map @ud [ship=@p app=term =path duc=duct])
heartbeat=(unit timer)
==
This is the state of a particular channel in the channel system.
modesays whether the channel sends/received JSON or nouns.stateis either the expiration time or the duct currently listening.next-idis the next event ID to be used in the event stream.last-ackis the date of the last client ack and is used for clog calculations in combination withunacked.eventsqueue contains all unacked events:idis the server-set event ID.request-idis the client-set request ID.$channel-event is the event itself.
unackedmapcontains the unacked event count perrequest-idand is used for clog calculations.subscriptionsmapcontains gall subscriptions byrequest-id.heartbeatis the SSE heartbeat $timer.
$binding
$binding+$ binding
$: site=(unit @t)
path=(list @t)
==A binding is a rule to match a URL path and optional site domain which can then be tied to an $action. A path of /foo will also match /foo/bar, /foo/bar/baz, etc. If the site is ~ it will be determined implicitly. A binding must be unique.
$action
$action +$ action
$% [%gen =generator]
[%app app=term]
[%authentication ~]
[%logout ~]
[%channel ~]
[%scry ~]
[%name ~]
[%four-oh-four ~]
==The action to take when a $binding matches an incoming HTTP request.
$generator
$generator+$ generator
$: =desk :: desk on current ship that contains the generator
path=(list @t) :: path on :desk to the generator's hoon file
args=* :: args: arguments passed to the gate
==This refers to a generator on a local ship that can handle requests. Note that serving generators via Eyre is not fully implmented and should not be used.
$http-config
$http-config+$ http-config
$: secure=(unit [key=wain cert=wain])
proxy=_|
log=?
redirect=?
==The configuration of the runtime HTTP server itself. The secure field contains the PEM-encoded RSA private key and certificate or certificate chain when using HTTPS, and otherwise is ~ when using plain HTTP. The proxy field is not currently used. The log field turns on HTTP(S) access logs but is not currently implemented. The redirect field turns on 301 redirects to upgrade HTTP to HTTPS if the key and cert are set in secure.
$http-rule
$http-rule+$ http-rule
$% [%cert cert=(unit [key=wain cert=wain])]
[%turf action=?(%put %del) =turf]
==This is for updating the server configuration. In the case of %cert, a cert of ~ clears the HTTPS cert & key, otherwise cert contains the PEM-encoded RSA private key and certificate or certificate chain. In the case of %turf, a %put action sets a domain name and a %del action removes it. The $turf contains the domain name.
$address
$address+$ address
$% [%ipv4 @if]
[%ipv6 @is]
==A client IP address.
$inbound-request
$inbound-request+$ inbound-request
$: authenticated=?
secure=?
=address
=request:http
==An inbound HTTP request and metadata. The authenticated field says whether the request was made with a valid session cookie. The secure field says whether it was made with HTTPS. The $address is the IP address from which the request originated, except if it came from localhost and included a Forwarded header, in which case it's the address specified in that header. The $request:http contains the HTTP request itself.
HTTP
$header-list:http
$header-list:http+$ header-list (list [key=@t value=@t])An ordered list of HTTP headers. The key is the header name e.g 'Content-Type' and the value is the value e.g. text/html.
$method:http
$method:http+$ method
$? %'CONNECT'
%'DELETE'
%'GET'
%'HEAD'
%'OPTIONS'
%'POST'
%'PUT'
%'TRACE'
==An HTTP method.
$request:http
$request:http+$ request
$: method=method
url=@t
=header-list
body=(unit octs)
==A single HTTP request. The $method:http is the HTTP method, the url is the unescaped URL, the $header-list:http contains the HTTP headers of the request and the body is the actual data. An octs is just [p=@ud q=@] where p is the byte-length of q, the data.
$response-header:http
$response-header:http+$ response-header
$: status-code=@ud
headers=header-list
==The status code and $header-list:http of an HTTP response.
$http-event:http
$http-event:http+$ http-event
$% $: %start
=response-header
data=(unit octs)
complete=?
==
$: %continue
data=(unit octs)
complete=?
==
[%cancel ~]
==Packetized HTTP.
Urbit treats Earth's HTTP servers as pipes, where Urbit sends or receives one or more http-events. The first of these will be a %start, and the last will always be %cancel or will have complete set to %.y to finish the connection.
Calculation of control headers such as 'Content-Length' or 'Transfer-Encoding' should be performed at a higher level; this structure is merely for what gets sent to or received from Earth.
$simple-payload:http
$simple-payload:http+$ simple-payload
$: =response-header
data=(unit octs)
==
--A simple, one-event response used for generators. The $reponse-header:http contains the status code and HTTP headers. The octs in the data contains the body of the response and is a [p=@ud q=@] where p is the byte-length of q, the data.
Last updated