You are looking at historical revision 12523 of this page. It may differ significantly from its current revision.
- Starting the server
- Configuration parameters
- Runtime information
- Virtual hosts
- Procedures and macros
A small web-server written in Chicken.
Spiffy is a web-server library for the Chicken Scheme system. It's quite easy to set up and use (whether as a library or a standalone server application) and it can be customized in numerous ways.
Starting the server[procedure] (start-server [port: port-number])
Starts the server, to listen on the given port. Other configuration can be tweaked through SRFI-39 parameters. These are listed below. Once the server is started, server behaviour can be controlled through these parameters as well. By default, Spiffy will only serve static files. On directories, it will give a "403 forbidden", unless there is an index-file. If there is, that file's contents will be shown.
All arguments directly supplied to start-server override the configuration parameter values.
Port-number defaults to the value of server-port (see below).
The following parameters can be used to control spiffy's behaviour. Besides these parameters, you can also influence spiffy's behaviour by tweaking the intarweb parameters.[parameter] (root-path [path])
The path to the document root. Defaults to "./web".[parameter] (server-port [port-number])
The port number on which to listen. Defaults to 8080.[parameter] (index-files [file-list])
A list of filenames which are to be used as index files to serve when the requested URL identifies a directory. Defaults to '("index.html" "index.xhtml")[parameter] (mime-type-map [extension->mimetype-list])
An alist of extensions (strings) to mime-types (symbols), to use for the content-type header when serving up a static file. Defaults to
The mime-type (a symbol) to use if none was found in the mime-type-map. Defaults to 'application/octet-stream[parameter] (default-host [hostname])
The host name to use when no virtual host could be determined from the request. See the section on virtual hosts below.[parameter] (vhost-map [host-regex->vhost-handler])
A mapping of virtual hosts (regex) to handlers (procedures of one argument; a continuation thunk). See the section on virtual hosts below. Defaults to `((".*" . ,(lambda (continue) (continue))))[parameter] (file-extension-handlers [extension->handler-list])
An alist mapping file extensions (strings) to handler procedures (lambdas of one argument; the file name relative to the webroot). Defaults to '(). If no handler was found, defaults to just sending a static file.
Besides "static" configuration, Spiffy also has several handlers for when something is to be served.[parameter] (handle-directory [proc])
The handler for directory entries. If the requested URL points to a directory which has no index file, this handler is invoked. It is a procedure of one argument, the path (a string) relative to the webroot. Defaults to a procedure which returns a "403 forbidden".[parameter] (handle-file [proc])
The handler for files. If the requested URL points to a file, this handler is invoked to serve the file. It is a procedure of one argument, the path (a string) relative to the webroot. Defaults to a procedure which sets the content-type and determines a handler based on the file-extension-handlers, or send-static-file if none was found.[parameter] (handle-not-found [proc])
The handler for nonexisting files. If the requested URL does not point to an existing file or directory, this procedure is called. It is a procedure of one argument, the path (a string) that was requested. This path should be interpreted as being relative to the webroot (even though it points to no existing file). Defaults to a procedure which returns a "404 Not found".
During the handling of a request, Spiffy adds more information to the environment by parameterizing the following parameters whenever the information becomes available:[parameter] (current-request [request])
An intarweb request-object that defines the current request. Available from the moment the request comes in and is parsed. Contains, among other things, the query parameters and the request-headers, in fully parsed form (as intarweb returns them).[parameter] (current-response [request])
An intarweb response-object that defines the current response. Available from the same time current-request is available. This keeps getting updated along the way, while the response data is being refined (like when headers are being added).[parameter] (current-file [path])
The path to the requested file (a string). Available from the moment Spiffy determined the requested URL points to a file (just before the handle-file procedure is called).[parameter] (current-pathinfo [path])
The trailing path fragments (a list of strings) that were passed in the URL after the requested filename. Available from the moment Spiffy determined the requested URL points to a file (just before the handle-file procedure is called).
Spiffy has support for virtual hosting, using the HTTP/1.1 Host header. This allows you to use one Spiffy instance running on one IP address/port number to serve multiple webpages, as determined by the hostname that was requested.
The virtual host is defined by a procedure, which can set arbitrary parameters on-the-fly. It is passed a continuation thunk, which it should explicitly call if it wants the processing to continue. The most used parameter in virtual host setups is the root-path parameter, so that another docroot can be selected based on the requested hostname, showing different websites for different hosts:
<example> <expr> (vhost-map `(("foo\\.bar\\.com" .
,(lambda (continue) (parameterize ((file-extension-handlers `(("ssp" . ,ssp-handler) ("ws" . ,web-scheme-handler))) (root-path "/var/www/domains/foo.bar.com")) (continue)))) (,(glob->regexp "*.domain.com") . ,(lambda (continue) (parameterize ((file-extension-handlers `(("php" . ,(cgi-handler* "/usr/pkg/bin/php")))) (root-path "/var/www/domains/domain.com")) (continue))))))
In this example, if a client accesses foo.bar.com/mumble/blah.html, the file /var/www/domains/foo.bar.com/mumble/blah.html will be served. Any files ending in .ssp or .ws will be served by the corresponding file type handler. If there's any PHP file, its source will simply be displayed. In case of my.domain.com/something/bar.html, the file /var/www/domains/domain.com/something/bar.html will be served. If there's a .ssp or .ws file there, it will not be interpreted. Its source will be displayed instead. A .php file, on the other hand, will be passed via CGI to the program /usr/pkg/bin/php.
Domain names are mapped to a lambda that sets up any parameters it wants to override from the defaults. The host names are matched using string-match. If the host name is not yet a regexp, it will be converted to a case-insensitive regexp.
Procedures and macros
The following procedures and macros can be used in dynamic web programs, or dynamic server configuration:[procedure] (with-headers new-headers thunk)
Call thunk with the header list new-headers. This parameterizes the current response to contain the new headers. The existing headers are extended with new-headers through intarweb's headers procedure.[procedure] (send-status code reason [message])
Easy way to send a page and a status code to the client. The optional message is a string containing HTML to add in the body of the response. Example:
<example> <expr> (send-status 404 "Not found"
"Sorry, page not found! Please try <a href='/search.ws'>our search page</a>")
</expr> </example>[procedure] (send-static-file filename)
Send a file to the client. This sets the content-length header and tries to send the file as quickly as possible to the client. The filename is interpreted relative to root-path.[procedure] (restart-request request)
Restart the entire request-handling starting at the point where the request was just parsed. The argument is the new request to use. Be careful, this makes it very easy to introduce unwanted endless loops!
This section will describe what the various modules that come with Spiffy are and how they work.
SSP, or Scheme Server Pages, are a way to embed Scheme in HTML pages. Files with an extension of .ssp are handled specifically, by replacing occurrences of certain reserved tags with Scheme code. There are two possible forms, either the long version, where all output is redirected to the HTTP response port, or the short, where the result of the embedded expression is displayed in the response. The tags default to <?scheme and <?, see Configuration for how to change them.
<html><body> <ol><?scheme (for-each (lambda (i) (printf "<li>~S~%" i)) (iota 5))?></ol> <br /> <b><?(call-with-values (lambda () (user-information (current-user-id))) (lambda (name . _) name))?><b> </body></html>
would generate for example something like this:
1. 0 2. 1 3. 2 4. 3 5. 4
(felix x 500 100 /home/felix /bin/bash)
When a .ssp file is loaded the first time, or when it has been modified, then a translation takes place that generates a loadable Scheme source file (with the extension .sspx, in the same directory as the original file) from the original data, so in the above example something like this would be generated:
(let () (display "<html><body>\n<ol>") (for-each (lambda (i) (printf "<li>~S~%" i)) (iota 5)) (display "</ol>\n<br />\n<b>") (display (call-with-values (lambda () (user-information (current-user-id))) (lambda (name . _) name))) (display "<b>\n</body></html>\n") )
Note that the body is evaluated in a (let () ...) form.
Note: each request runs in a separate thread, so code in .ssp pages should take care when using global variables.
The SSP handler can be configured with the following options:[parameter] (ssp-short-open-tag [tag-regexp])
The opening tag for short fragments. Default: <?[parameter] (ssp-long-open-tag [tag-regexp])
The opening tag for long fragments. Default: <?scheme[parameter] (ssp-close-tag [tag-regexp])
The closing tag for Scheme fragments in .ssp files. Default: ?>[parameter] (ssp-eval-environment [environment])
The environment passed to eval when evaluating Scheme code inside .ssp-pages. Default: interaction-environment
For the duration of evaluating a SSP page, the following parameters will have a value assigned to them:[parameter] (current-workdir [path])
During execution, the current working directory of the SSP handler. Any of the "include" procedures (ssp-include, ssp-stringize) will interpret their file arguments to be relative to this directory.[parameter] (exit-handler [handler])
During execution of an ssp page, exit-handler is bound to a procedure that will finish the current page, ignoring any further content or code.
The ssp-handler module adds the following procedures to the environment:[procedure] (ssp-handler filename)
The handler itself, which should be used in the file-extension-handlers parameter list.[procedure] (ssp-include filename)
Translates the file filename into Scheme by replacing <?scheme ... ?> and <? ... ?> sequences (if needed) and writes the translated contents to the current output-port.[procedure] (ssp-stringize FILENAME)
Similar to ssp-include, but instead of writing the translated text, the text is returned as a string.
Another way of executing Scheme code to produce content are .ws files: these should contain a Scheme expression that is expected to evaluate to a string which will be directly written as the response to the current request. This facility is intended for Scheme code that uses the web-scheme extension.
You can use the web-scheme-handler for any Scheme file which returns HTML as a string or which has a side-effect of outputting the HTML. If it's the latter, make sure the final statement in your file does not return a string or it will be appended to the output (just like in the csi REPL).
Tip This handler type is perfect not only for web-scheme but also for when you're using SRV:send-reply with SXML or for example a wiki-to-string translator.
Note: each request runs in a separate thread, so code in .ws pages should take care when using global variables.
Note: web-scheme-handler is a separate extension and must be imported as such.
The Web-scheme handler can be configured with the following options:[parameter] (web-scheme-eval-environment [environment])
The environment passed to eval when evaluating Scheme code inside .ws-pages. Default: interaction-environment
The Web-scheme handler adds only one procedure to the environment:[procedure] (web-scheme-handler filename)
The handler itself, which should be used in the file-extension-handlers parameter list.
Spiffy supports CGI/1.1 as specified by RFC 3875.
All request headers will be passed as environment variables to the CGI program, prefixed with "HTTP_", and converted to uppercase, with hyphens ("-") replaced by an underscore ("_"). The CGI program will receive the request body in unparsed form from stdin and should write a complete HTTP response to stdout. Any headers that are missing but required for HTTP will be added by Spiffy. For more info on how a CGI script is called, consult the spec.
The AUTH_TYPE and REMOTE_USER environment variables are currently not set during invocation of CGI subprocesses. The REMOTE_IDENT environment variable is not and never will be supported.
CGI handler can be configured with the following parameters:[procedure] (cgi-default-environment [env-alist])
The environment variables that should be in the default environnment of every CGI program. Variables like SCRIPT_NAME will be added dynamically to the end of this alist.
(("SERVER_SOFTWARE" . ,(server-software)) ("GATEWAY_INTERFACE" . "CGI/1.1"))
CGI-handler adds two procedures to the environment:[procedure] (cgi-handler filename [interpreter])
The cgi-handler procedure is called by cgi-handler* with the filename. It's not very useful on its own.[procedure] (cgi-handler* [interpreter])
The cgi-handler* procedure is usually more useful. It allows you to define an interpreter to use for files and returns a file handler. See the example above for file-extension-handlers.
In order to get directory listings, you can use simple-directory-handler. Just assign the simple-directory-handler to handle-directory and you're set.
The simple directory handler has a few configuration options:[procedure] (simple-directory-dotfiles? [dotfiles?])
Determines if dotfiles should show up in the directory listings. Default: #f[procedure] (simple-directory-display-file [displayer])
A lambda that accepts three arguments: the remote filename, the local filename and a boolean that says if the file is a directory. This lambda should output a table row with the desired information. Defaults to a lambda that prints the name, size and date when the file was last modified.
The simple-directory handler adds only one procedure to the environment:[procedure] (simple-directory-handler pathname)
The handler itself, which should be used in the handle-directory parameter.
- 4.0 Rewrite from scratch, using Intarweb
- pre-4.0 See the changelog for the old spiffy
Copyright (c) 2005-2008, Felix L. Winkelmann and Peter Bex All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.