Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added explanation of HTTP_* keys computing #16

Merged
merged 1 commit into from
Jun 25, 2011
Merged

Added explanation of HTTP_* keys computing #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions PSGI.pod
View file
Open in desktop
Original file line number Original file line Diff line number Diff line change
Expand Up @@ -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 correspond to the presence or absence of the appropriate HTTP header
in the request. 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 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 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>. with C<, >, as in L<RFC 2616|http://www.ietf.org/rfc/rfc2616>.
Expand Down