Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Added explanation of HTTP_* keys computing #16

Merged
merged 1 commit into from

2 participants

@polettix

Hi, I tried to explain how HTTP_* keys are set by the server because I did not find any trace in the specs. It seems to be performed according to the CGI specs, so I tried to document it keeping this in mind.

Cheers, Flavio.

@miyagawa
Owner

Looks good.

@miyagawa miyagawa merged commit b401396 into plack:master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Jun 25, 2011
  1. @polettix
This page is out of date. Refresh to see the latest.
Showing with 5 additions and 0 deletions.
  1. +5 −0 PSGI.pod
View
5 PSGI.pod
@@ -196,6 +196,11 @@ HTTP request headers. The presence or absence of these keys should
correspond to the presence or absence of the appropriate HTTP header
in the request.
+The key is obtained converting the HTTP header field name to upper
+case, replacing all occurrences of hyphens C<-> with
+underscores C<_> and prepending C<HTTP_>, as in
+L<RFC 3875|http://www.ietf.org/rfc/rfc3875>.
+
If there are multiple header lines sent with the same key, the server
should treat them as if they were sent in one line and combine them
with C<, >, as in L<RFC 2616|http://www.ietf.org/rfc/rfc2616>.
Something went wrong with that request. Please try again.