---
postid: 000
-title: Hunchentoot: requests and replies
+title: Hunchentoot: requests and replies [a]
date: August 23, 2019
author: Lucian Mogoșanu
tags: tech, tmsr
Note that (somewhat counter-intuitively) request parsing and object
creation doesn't occur in request.lisp, but upstream in
-[process-connection][ht-pc], and more specifically headers are parsed
-in headers.lisp, in [get-request-data][ht-iv-grd][^3]. So then what
-does request.lisp do? Well, it: defines the data structure; implements
-a lot of scaffolding for GET and POST parameter parsing; implements a
+[process-connection][ht-pc]; more specifically, headers are parsed in
+headers.lisp, in [get-request-data][ht-iv-grd][^3]. So then what does
+request.lisp do? Well, it: defines the data structure; implements a
+lot of scaffolding for GET and POST parameter parsing; implements a
user interface for request handlers; and finally, it creates a context
in which request handlers can be safely executed, i.e. if something
fails, execution can be unwound to the place where
[handle-request][ht-hr] was called and an error response can be logged
and returned. Let's look at each of these pieces.
-<a name="ch" href="#ch">[ch]</a> [**convert-hack**][ht-ch]:
-
-<a name="prfd" href="#prfd">[prfd]</a>
-[**parse-rfc2388-form-data**][ht-prfd]:
-
-<a name="gpd" href="#gpd">[prfd]</a> [**get-post-data**][ht-gpd]:
+The first set of functions deals with parameter parsing. In
+particular, GET parameter parsing is performed when a request object
+is instantiated, while POST parameters are parsed on request,
+i.e. when the accessor method is called. Let's see:
<a name="ii2" href="#ii2">[ii2]</a> [**initialize-instance**][ht-ii2]:
-
-<a name="pr" href="#pr">[pr]</a> [**process-request**][ht-pr]:
-
-<a name="wrp" href="#wrp">[wrp]</a> [**within-request-p**][ht-wrp]:
-
-<a name="mrpp" href="#mrpp">[mrpp]</a>
-[**maybe-read-post-parameters**][ht-mrpp]:
-
-<a name="rrp" href="#rrp">[rrp]</a>
-[**recompute-request-parameters**][ht-rrp]:
-
-<a name="sns" href="#sns">[sns]</a> [**script-name\***][ht-sns]:
-
-<a name="qss" href="#sns">[qss]</a> [**query-string\***][ht-qss]:
-
-<a name="gps" href="#gps">[gps]</a> [**get-parameters\***][ht-gps]:
-
-<a name="pp" href="#pp">[pp]</a> [**post-parameters**][ht-pp]:
-
-<a name="pps" href="#pps">[pps]</a> [**post-parameters\***][ht-pps]:
-
-<a name="his" href="#his">[his]</a> [**headers-in\***][ht-his]:
-
-<a name="cis" href="#cis">[cis]</a> [**cookies-in\***][ht-cis]:
-
-<a name="hi" href="#hi">[hi]</a> [**header-in**][ht-hi]:
-
-<a name="his2" href="#his2">[his2]</a> [**header-in\***][ht-his2]:
-
-<a name="a" href="#a">[a]</a> [**authorization**][ht-a]:
-
-<a name="ras" href="#ras">[ras]</a> [**remote-addr\***][ht-ras]:
-
-<a name="rps" href="#rps">[rps]</a> [**remote-port\***][ht-rps]:
-
-<a name="las" href="#las">[las]</a> [**local-addr\***][ht-las]:
-
-<a name="lps" href="#lps">[lps]</a> [**local-port\***][ht-lps]:
-
-<a name="rra" href="#rra">[rra]</a> [**real-remote-addr**][ht-rra]:
-
-<a name="h" href="#h">[h]</a> [**host**][ht-h]:
-
-<a name="rus" href="#rus">[rus]</a> [**request-uri\***][ht-rus]:
-
-<a name="rms" href="#rms">[rms]</a> [**request-method\***][ht-rms]:
-
-<a name="sps" href="#sps">[sps]</a> [**server-protocol\***][ht-sps]:
-
-<a name="ua" href="#ua">[ua]</a> [**user-agent**][ht-ua]:
-
-<a name="ci" href="#ci">[ci]</a> [**cookie-in**][ht-ci]:
-
-<a name="r" href="#r">[r]</a> [**referer**][ht-r]:
-
-<a name="gp" href="#gp">[gp]</a> [**get-parameter**][ht-gp]:
-
-<a name="pp" href="#pp">[pp]</a> [**post-parameter**][ht-pp]:
-
-<a name="p" href="#p">[p]</a> [**parameter**][ht-p]:
-
-<a name="hims" href="#hims">[hims]</a> [**handle-if-modified-since**][ht-hims]:
+Similarly to other pieces of code [under review][ht-otpct-ii], this is
+an ":after" method which gets called immediately after an object
+instantiation. a. an error handling context is defined; in which
+b. [script-name][ht-sn] and [query-string][ht-qs] are set based on the
+request URI[^4]; c. [get-parameters][ht-gp] are set[^5]; d.
+[cookies-in][ht-ci-acc] are set[^6]; e. [session][ht-sess] is set[^7];
+and finally, if everything fails, [log-message\*][ht-lms] is called to
+log the error and [return-code\*][ht-rcs] is set to http-bad-request.
+
+By the way, since HTTP hasn't escaped Unicode, URL decoding needs a
+character format, which is determined based on the content-type field
+in the header, which is determined using the
+[external-format-from-content-type][ht-effct] function.
<a name="effct" href="#effct">[effct]</a>
-[**external-format-from-content-type**][ht-effct]:
-
-<a name="rpd" href="#rpd">[rpd]</a> [**raw-post-data**][ht-rpd]:
+[**external-format-from-content-type**][ht-effct]: Takes a
+content-type string as an argument; if this argument is non-nil, then
+take the charset from [parse-content-type][ht-pct][^8]; and try to
+convert the result into a flexi-streams "external-format" via
+[make-external-format][flex-mef]. If this fails, send a
+[warning][ht-hw].
-<a name="arv" href="#arv">[arv]</a> [**aux-request-value**][ht-arv]:
-
-<a name="darv" href="#darv">[darv]</a> [**delete-aux-request-value**][ht-darv]:
-
-<a name="pp2" href="#pp2">[pp2]</a> [**parse-path**][ht-pp2]:
+<a name="mrpp" href="#mrpp">[mrpp]</a>
+[**maybe-read-post-parameters**][ht-mrpp]: This does quite a bit of
+checking on the parameters it receives, namely it only does something
+when: the content-type header is set; and the request method is POST;
+and [the "force" parameter is set; or the [raw-post-data][ht-rpd-slot]
+slot is not set]; and the [raw-post-data][ht-rpd-slot] slot is not
+true -- to quote from a comment, "can't reparse multipart posts, even
+when FORCEd". Furthermore, for the function to do anything, the
+content-length header must be set or [input chunking][ht-icp] must be
+enabled; otherwise, a warning is logged and the function returns.
+
+If all checks pass, then wrapped in a condition handler:
+a. [parse-content-type][ht-pct] (see [footnote #8](#fn8) for details),
+yielding a type, subtype and charset; b. try [making][flex-mef] an
+external-format based b1. on the external-format parameter, and b2. on
+the charset found at (a), and b3. if all fails, fall back to
+[\*hunchentoot-default-external-format\*][ht-shdefs].
+
+Once we have an external-format, c. populate the
+[post-parameters][ht-pp-slot] slot: c1. if content-type is
+"application/x-www-form-urlencoded", then use
+form-url-encoded-list-to-alist (see [footnote #5](#fn5)); otherwise
+c2. the content-type is "multipart/form-data", which is parsed using
+[parse-multipart-form-data](#pmfd).
+
+Finally, d. if something fails in one of the previous steps, then
+d1. an error is logged; d2. the return-code is set to
+http-bad-request; and d3. the request is [aborted][ht-arh].
+
+<a name="pmfd" href="#pmfd">[pmfd]</a>
+[**parse-multipart-form-data**][ht-pmfd]: a. in a condition-handling
+context; b. make a new content-stream with the external-format set to
+latin-1[^9]; then on that content-stream,
+c. [parse-rfc2388-form-data](#prfd); then d. [get-post-data](#gpd);
+and e. if the result from (d) is a non-empty string, it's considered
+"stray data" and reported; finally, f. if an error occurs, it's logged
+and nothing is returned.
+
+Otherwise, the result from (c) is returned, as per
+[prog1][clhs-prog1].
-<a name="rp" href="#rp">[rp]</a> [**request-pathname**][ht-rp]:
+<a name="prfd" href="#prfd">[prfd]</a>
+[**parse-rfc2388-form-data**][ht-prfd]: Fortunately for us, parsing
+multipart-blah-blah is encapsulated in yet another [RFC][rfc-2388] of
+its own, for which there already exists a CL
+"library"[^10]. Unfortunately, the coad written around said "library"
+is still kludgy. Let's see.
+
+a. parse the content-type header; then b. look for a "boundary"
+content-type parameter, and return empty-handed if that doesn't exist;
+otherwise c. for each MIME part; d. get the MIME headers; and
+e. particularly, the content-disposition header; and f. particularly,
+the "name" field of that header.
+
+g. when the item at (f) exists, append the following to the result:
+g1. the item at (f), converted using [convert-hack](#ch); and g2. the
+contents, converted using the same [convert-hack](#ch). However,
+mime-part-contents can return either[^11] g2i. a path to a local file,
+in which case the coad stores the path, the (converted) filename and
+its content-type; or g2ii. a string, in which case the (converted)
+string is stored.
+
+<a name="ch" href="#ch">[ch]</a> [**convert-hack**][ht-ch]: You might
+have been wondering what this does and why the fuck it exists in the
+first place. Let's quote from the documentation itself:
+
+> The rfc2388 package is buggy in that it operates on a character
+> stream and thus only accepts encodings which are 8 bit
+> transparent. In order to support different encodings for parameter
+> values submitted, we post process whatever string values the rfc2388
+> package has returned.
+
+I don't know what the fuck "8 bit transparent" means, but the function
+does exactly this: it converts the input string to a raw vector of
+octets, then converts said vector (using [octets-to-string][flex-ots])
+to a string of the encoding given by the external-format parameter. So
+this is just dancing around the previous [latin1](#pmfd) game -- yes,
+if you send a UTF-8-encoded file wrapped in a (ISO-8859-1-encoded)
+POST request, the result will be mixed-encoded data, and whoever gets
+this will have to make heads and tails of the resulting pile of shit.
+
+I *can't wait* for the moment when the ban on this multipart fungus
+comes into effect, it'll be a joyous day.
+
+<a name="gpd" href="#gpd">[gpd]</a> [**get-post-data**][ht-gpd]: Reads
+data from the request stream and sets the [raw-post-data][ht-rpd-slot]
+slot:
+
+a. if the want-stream argument is set, then the stream is converted to
+latin-1-encoded (as per above) and the slot is set to this stream,
+bound by the content-length (if this field exists).
+
+b. if content-length is set and it's greater than the already-read
+argument -- i.e. there is still data to be read from the stream,
+assuming the user has already read some of it -- then check whether
+[chunking][ht-icp] is enabled and log a warning if so; and read the
+content and let it be assigned.
+
+c. if [chunking][ht-icp] is enabled, then c1. setup two arrays: an
+adjustable "content" array and a buffer; c2. setup a position marker
+for the content array; c3. read into the buffer; then c4. adjust the
+content array to the new size; then c5. copy data from the buffer into
+the content array at the current position; and finally, c6. stop when
+there's no more content to be read.
+
+I'm running out of space (and time) here, so contrary to [the
+schedule][tmsr-work-iv] I'm splitting this into two pieces, the second
+part to be published next week. Annoyingly enough, this is also
+delaying [other work][logs-ttp-comments], including the fabled
+tarpitian-comment-server, so for now the venue for comments remains
+[#spyked][contact].
[^1]: In practice some c in C can also be a s in S and vice-versa, why
not? In a sane world C and S would be the same set, and thus our
Now how 'bout *you* get a blog and start doing this for the coad
that you're using? Wouldn't that be neat?
+[^4]: Given an URI of the general form
+ http://my-resource.tld?p1=v1&p2=v2..., script-name denotes the
+ part before the question mark, while query-string denotes the part
+ after it.
+
+[^5]: The query-string is split by ampersands and passed to
+ [form-url-encoded-list-to-alist][ht-fuelta], which takes this list
+ and splits each element by "equals". Thus the string
+ p1=v1&p2=v2... ends up being represented as the association list:
+
+ ~~~~ {.commonlisp}
+ (("p1" . "v1") ("p2" . "v2") ...)
+ ~~~~
+
+[^6]: The process is similar to the previous footnote. The cookie
+ string is split and passed to [cookies-to-alist][ht-cta] which
+ does pretty much the same thing as the previously-described
+ function, only there's no URL decoding going on.
+
+[^7]: I've set to deliberately omit this part since the beginning, so
+ I won't go into details here.
+
+[^8]: Did I by any chance mention HTTP has grown into a tumour-like
+ structure? As but one of many examples of malignant cells: the
+ "content-type" field contains a type/subtype part
+ (e.g. "text/plain", or "application/octet-stream" or whatever);
+ but it also contains *parameters*, such as a charset, or
+ "multipart" markers, into which I won't get, because my blood
+ pressure is already going up.
+
+ Anyway, [parse-content-type][ht-pct] reads all these and returns a
+ type, a subtype and a charset, if it exists.
+
+ By the by, unlike the previous footnotes, the "parameter" alist is
+ constructed using Chunga's [read-name-value-pairs][chunga-rnvp],
+ which seems to do more or less the same thing as those
+ functions. So where the fuck does all this duplication come from?
+
+[^9]: This looks confusing after all the previous "external-format"
+ fudge. Note that *the content* has a user-provided format, while
+ the multipart-blah-blah thing is [by default][rfc-1945-3-6-1]
+ Latin1. This is not fucking amusing, I know.
+
+[^10]: Written by one Janis Dzerins. There's also a
+ variation/"improvement" on this coad, rfc-2388-binary, which is
+ used by another Lisp piece that I have on my disk, I forgot which
+ one.
+
+ Speaking of which, I expect I'll run into more of these "duplicate
+ libraries" problems in the future, which will require
+ porting/adaptation work. No, I'm not gonna use a thousand
+ libraries for XML parsing, there's [one][s-xml], and that's it. If
+ you're gonna complain, then you'd better have a good reason; where
+ the fuck were you when I needed that code?
+
+[^11]: Y'know, I didn't set out to review *this* piece of code back
+ when I started this, but it can't be helped. mime-part-contents is
+ the "-contents" part of a [defstruct][r2388-mp] built using
+ [parse-mime][r2388-pm]. Now, this code behaves in (what I believe
+ to be) a very odd manner, namely: when it encounters arbitrary
+ string input, it returns it as-is; the alternative is to encounter
+ a MIME part that contains a filename field, in which case this
+ coad creates a new temporary file and stores the content there; in
+ this case, the mime-part structure will contain a bunch of headers
+ and a *path* to the contents, which is an unexpected extra layer
+ of indirection, because why the fuck not.
+
+ This behaviour can be overriden by setting the
+ "write-content-to-file" parameter to nil. However, this is the
+ *default* behaviour, and what Hunchentoot expects. Fuck my life.
+
[chunking]: /posts/y06/098-hunchentoot-iv.html#fn2
[tcp]: /posts/y05/096-hunchentoot-ii.html#fn1
[alf-cl-on-pc]: http://trilema.com/2019/trilema-goes-dark/#comment-130686
[rfc-1945-5]: https://tools.ietf.org/html/rfc1945#section-5
[rfc-1945-6]: https://tools.ietf.org/html/rfc1945#section-6
[ht-c-req]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L31
+[ht-ci-acc]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L68
+[ht-gp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L71
+[ht-pp-slot]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L75
+[ht-sn]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L79
+[ht-qs]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L83
+[ht-sess]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L86
+[ht-rpd-slot]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L94
[ht-ch]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L118
[ht-prfd]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L127
[ht-gpd]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L150
[ht-ii2]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L185
-[ht-pr]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L219
-[ht-wrp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L262
[ht-pmfd]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L266
[ht-mrpp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L282
-[ht-rrp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L334
-[ht-sns]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L344
-[ht-qss]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L349
-[ht-gps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L354
-[ht-pp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L359
-[ht-pps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L368
-[ht-his]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L373
-[ht-cis]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L378
-[ht-hi]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L383
-[ht-his2]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L389
-[ht-a]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L394
-[ht-ras]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L407
-[ht-rps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L411
-[ht-las]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L415
-[ht-lps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L419
-[ht-rra]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L423
-[ht-h]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L433
-[ht-rus]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L437
-[ht-rms]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L441
-[ht-sps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L445
-[ht-ua]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L449
-[ht-ci]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L453
-[ht-r]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L458
-[ht-gp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L462
-[ht-pp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L467
-[ht-p]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L472
-[ht-hims]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L480
[ht-effct]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L495
-[ht-rpd]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L508
-[ht-arv]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L551
-[ht-arv2]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L559
-[ht-darv]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L576
-[ht-pp2]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L585
-[ht-rp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L613
[ht-pc]: /posts/y06/098-hunchentoot-iv.html#pc
[ht-iv-grd]: /posts/y06/098-hunchentoot-iv.html#fn3
[ht-hr]: /posts/y06/098-hunchentoot-iv.html#hr
+[ht-otpct-ii]: /posts/y06/09b-hunchentoot-v.html#otpct-ii
+[ht-fuelta]: http://coad.thetarpit.org/hunchentoot/c-util.lisp.html#L244
+[ht-cta]: http://coad.thetarpit.org/hunchentoot/c-util.lisp.html#L255
+[ht-lms]: /posts/y06/098-hunchentoot-iv.html#lms
+[ht-rcs]: http://coad.thetarpit.org/hunchentoot/c-reply.lisp.html#L103
+[ht-pct]: http://coad.thetarpit.org/hunchentoot/c-util.lisp.html#L283
+[flex-mef]: http://edicl.github.io/flexi-streams/#make-external-format
+[ht-hw]: http://coad.thetarpit.org/hunchentoot/c-conditions.lisp.html#L58
+[chunga-rnvp]: https://edicl.github.io/chunga/#read-name-value-pairs
+[ht-icp]: http://coad.thetarpit.org/hunchentoot/c-util.lisp.html#L342
+[ht-shdefs]: http://coad.thetarpit.org/hunchentoot/c-specials.lisp.html#L275
+[ht-arh]: /posts/y06/098-hunchentoot-iv.html#selection-762.0-762.5
+[rfc-1945-3-6-1]: https://tools.ietf.org/html/rfc1945#section-3.6.1
+[clhs-prog1]: http://clhs.lisp.se/Body/m_prog1c.htm
+[rfc-2388]: https://tools.ietf.org/html/rfc2388
+[s-xml]: /posts/y05/086-s-xml.html
+[r2388-mp]: http://coad.thetarpit.org/rfc2388/c-rfc2388.lisp.html#L404
+[r2388-pm]: http://coad.thetarpit.org/rfc2388/c-rfc2388.lisp.html#L415
+[flex-ots]: http://edicl.github.io/flexi-streams/#octets-to-string
+[tmsr-work-iv]: /posts/y06/099-tmsr-work-iv.html#selection-120.0-120.3
+[logs-ttp-comments]: http://logs.nosuchlabs.com/log/trilema/2019-08-16#1929229
+[contact]: http://webchat.freenode.net/?channels=#spyked&nick=f_thetarpit_09c
--- /dev/null
+---
+postid: 000
+title: Hunchentoot: requests and replies [b]
+date: August 30, 2019
+author: Lucian Mogoșanu
+tags: tech, tmsr
+---
+
+<a name="pr" href="#pr">[pr]</a> [**process-request**][ht-pr]:
+
+<a name="wrp" href="#wrp">[wrp]</a> [**within-request-p**][ht-wrp]:
+
+<a name="rrp" href="#rrp">[rrp]</a>
+[**recompute-request-parameters**][ht-rrp]:
+
+<a name="sns" href="#sns">[sns]</a> [**script-name\***][ht-sns]:
+
+<a name="qss" href="#qss">[qss]</a> [**query-string\***][ht-qss]:
+
+<a name="gps" href="#gps">[gps]</a> [**get-parameters\***][ht-gps]:
+
+<a name="pp" href="#pp">[pp]</a> [**post-parameters**][ht-pp]:
+
+<a name="pps" href="#pps">[pps]</a> [**post-parameters\***][ht-pps]:
+
+<a name="his" href="#his">[his]</a> [**headers-in\***][ht-his]:
+
+<a name="cis" href="#cis">[cis]</a> [**cookies-in\***][ht-cis]:
+
+<a name="hi" href="#hi">[hi]</a> [**header-in**][ht-hi]:
+
+<a name="his2" href="#his2">[his2]</a> [**header-in\***][ht-his2]:
+
+<a name="a" href="#a">[a]</a> [**authorization**][ht-a]:
+
+<a name="ras" href="#ras">[ras]</a> [**remote-addr\***][ht-ras]:
+
+<a name="rps" href="#rps">[rps]</a> [**remote-port\***][ht-rps]:
+
+<a name="las" href="#las">[las]</a> [**local-addr\***][ht-las]:
+
+<a name="lps" href="#lps">[lps]</a> [**local-port\***][ht-lps]:
+
+<a name="rra" href="#rra">[rra]</a> [**real-remote-addr**][ht-rra]:
+
+<a name="h" href="#h">[h]</a> [**host**][ht-h]:
+
+<a name="rus" href="#rus">[rus]</a> [**request-uri\***][ht-rus]:
+
+<a name="rms" href="#rms">[rms]</a> [**request-method\***][ht-rms]:
+
+<a name="sps" href="#sps">[sps]</a> [**server-protocol\***][ht-sps]:
+
+<a name="ua" href="#ua">[ua]</a> [**user-agent**][ht-ua]:
+
+<a name="ci" href="#ci">[ci]</a> [**cookie-in**][ht-ci]:
+
+<a name="r" href="#r">[r]</a> [**referer**][ht-r]:
+
+<a name="gp" href="#gp">[gp]</a> [**get-parameter**][ht-gp]:
+
+<a name="pp2" href="#pp2">[pp2]</a> [**post-parameter**][ht-pp2]:
+
+<a name="p" href="#p">[p]</a> [**parameter**][ht-p]:
+
+<a name="hims" href="#hims">[hims]</a> [**handle-if-modified-since**][ht-hims]:
+
+<a name="rpd" href="#rpd">[rpd]</a> [**raw-post-data**][ht-rpd]:
+
+<a name="arv" href="#arv">[arv]</a> [**aux-request-value**][ht-arv]:
+
+<a name="darv" href="#darv">[darv]</a> [**delete-aux-request-value**][ht-darv]:
+
+<a name="pp3" href="#pp3">[pp3]</a> [**parse-path**][ht-pp3]:
+
+<a name="rp" href="#rp">[rp]</a> [**request-pathname**][ht-rp]:
+
+[ht-pr]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L219
+[ht-wrp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L262
+[ht-rrp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L334
+[ht-sns]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L344
+[ht-qss]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L349
+[ht-gps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L354
+[ht-pp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L359
+[ht-pps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L368
+[ht-his]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L373
+[ht-cis]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L378
+[ht-hi]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L383
+[ht-his2]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L389
+[ht-a]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L394
+[ht-ras]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L407
+[ht-rps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L411
+[ht-las]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L415
+[ht-lps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L419
+[ht-rra]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L423
+[ht-h]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L433
+[ht-rus]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L437
+[ht-rms]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L441
+[ht-sps]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L445
+[ht-ua]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L449
+[ht-ci]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L453
+[ht-r]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L458
+[ht-gp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L462
+[ht-pp2]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L467
+[ht-p]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L472
+[ht-hims]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L480
+[ht-rpd]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L508
+[ht-arv]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L551
+[ht-arv2]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L559
+[ht-darv]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L576
+[ht-pp3]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L585
+[ht-rp]: http://coad.thetarpit.org/hunchentoot/c-request.lisp.html#L613
projects / thetarpit.git / commitdiff