Get desktop application:
View/edit binary Protocol Buffers messages
Send a HTTP session auth token to the helper (Kismet->Helper) This lets the helper access administrative functions on the server without having to pass an actual login password
Request an auth token be sent in a HttpAuthToken frame
(message has no fields)
Define an endpoint (Helper->Kismet) Registers a HTTP endpoint; requests to this endpoint will be sent to the helper via the HttpRequest message, which will, in turn, expect replies via the HttpResponse message.
Full URI, including file type; Helpers cannot take advantage of the Kismet multi-serialization types so they must define a URI for each type
Method; ie GET or POST; a URI can only implement a single method and must register multiple URIs for multiple methods.
Authentication - does the URI require authentication? The proxy can handle this automatically.
Handle an incoming HTTP request (Kismet->Helper)
Unique ID of request, must be returned in the HttpResponse
Full URI of request
Method
If post, a map of post variables
Cancel an existing request (remote end went away)
Unique ID of request
Respond to HTTP data (Helper->Kismet)
Unique ID of request we're responding to
Headers being sent, if any
Content being sent, if any
Result code, if we're concluding this connection
Is this the end of this connection?
Sub-block of headers to send with the first response
Used in:
Header type to send
Content of header
Sub-block of HTTP data, per-field
Used in:
GET or POST field sent to Kismet
Content of GET or POST data, as parsed by microhttpd