[document request-send-headers a little
dan**20031202032707] {
hunk ./doc/handlers.html 60
-that was used for discrimination.
+that was used for discrimination.  You can get at the unmatched part
+of the URL string using REQUEST-UNHANDLED-PART
hunk ./doc/handlers.html 72
+<p>An HTTP response consists of a header and a body, and it's strongly
+recommended that you write the header using REQUEST-SEND-HEADERS.
+It returns the resonse code.
+
+REQUEST-SEND-HEADERS copes automatically with HTTP/0.9 requests and
+will also help you with conditional GETs if you ask it to: if you
+supply :conditional t and :last-modified some-universal-time, it will
+check for an If-Modified-Since header in the request, and send a 304
+if the response has been sent before.  Note that in this situation it
+is your responsibility to check the return value and bail if
+necessary: RFC 2616 states that "The 304 response MUST NOT contain a
+message-body, and thus is always terminated by the first empty line
+after the header fields"
+
+
hunk ./doc/handlers.html 90
-<a href="../example.lisp">example</a>.  For a list of condition names,
+<a href="example.lisp">example</a>.  For a list of condition names,
}