Global parameters

parameter: scgi:max-request-length

Examined by the default "POST" request method handler to determine whether the request is accepted. See scgi:request-method-handler

procedure: (scgi:request-method-handler (name <string>)) => <procedure-class>
procedure: (scgi:request-method-handler (name <string>) (proc <procedure-class>)) => <void>

Gets or sets an entry in the global hash table of request method handlers. name is a string identifying the request method and proc, if given, is a procedure of two arguments, the hash table containing the environment variables passed from the server and the response handler to call, which has no significant return value. The procedure is called with input and output ports connected to the webserver.

Handlers for the "GET" and "POST" methods are already registered, so you will probably seldomly register additional ones.

The default "POST" handler calls on methods registered by scgi:request-parameter-parser to parse the request parameters. Before it does so, it checks the content length of the request against (scgi:max-request-length). The request is rejected with an appropriate HTTP error status, if (scgi:max-request-length) is not #f and the content length is either not specified by the client or less than (scgi:max-request-length).

Modifications made to the table of request method handlers are thread safe, but the table is global.

procedure: (scgi:request-parameter-parser (name <string>)) => <procedure-class>
procedure: (scgi:request-parameter-parser (name <string>) (proc <procedure-class>)) => <void>

Gets or sets an entry in the global hash table of request parameter parsers. name is a string identifying the MIME-type to parse and proc, if given, is a procedure of two arguments, the hash table containing the environment variables passed from the server and the content length to read (which may be #f if no content length was sent by the client), which should return a hash table of decoded request parameters. The procedure is called with input and output ports connected to the webserver.

A handler for the "application/x-www-form-urlencoded" type is already registered. You may want to register one for multipart formdata if you want to use file uploads.

Modifications made to the table of request parameter parsers are thread safe, but the table is global.

parameter: scgi:resources

This parameter stores a hash table mapping PATH_INFO values passed in the environment to your SCGI application to response handler procedures. The hash table is wrapped up in a mutex and access to it is synchronized. You can initialize the parameter directly with a mutex, a hash table or with an association list, but it is recommended that you use the methods below to access it.

The handler procedures are procedures of two arguments, the server environment and the parsed request parameters as hash tables, and their return value has no meaning. The procedures are called with input and output ports connected to the webserver.

procedure: (scgi:add-resource (name <string>) (proc <procedure-class>)) => <void>
procedure: (scgi:add-resource (names <list of strings>) (proc <procedure-class>)) => <void>

Adds a response handler for the given resource(s) to the hash table in scgi:resources.

procedure: (scgi:find-resource (name <string>) (proc <procedure-class>)) => <procedure-class>

Returns the response handler for the given resource or #f if no handler exists for it.

procedure: (scgi:remove-resource (name <string>) (proc <procedure-class>)) => <void>
procedure: (scgi:remove-resource (names <list of strings>) (proc <procedure-class>)) => <void>

Removes the response handler(s) for the given resource(s) from the hash table in scgi:resources.

Assistance for output of content

Creating and running the server

procedure: (scgi:make-server (listener <tcp-listener>) #!optional (max-requests <exact>)) => <procedure-class>

Calls on make-tcp-server to create a procedure that will start the SCGI server when called.