Phillip J. Eby ha scritto:
> [...]
>> Note that some of these headers are response headers, and it is
>> responsibility of the WSGI application to properly folding them, and not
>> of the WSGI gateway.
>
> On the contrary. The gateway is responsible for sending *all* the
> header lines to the cl
At 10:27 PM 10/2/2007 +0200, Manlio Perillo wrote:
>Robert Brewer ha scritto:
> >
> > [...]
> > As you note, it's part of the HTTP spec that such headers
> > can be combined without changing the semantics. Here's a list of the
> > headers that need to be folded:
> >
> > comma_separated_headers = [
Phillip J. Eby ha scritto:
> At 10:03 PM 10/2/2007 +0200, Manlio Perillo wrote:
>> Manlio Perillo ha scritto:
>> > [...]
>> > As an example Nginx stores all the headers in a associative array,
>> > where, of course, only the "last seen" headers appears.
>> >
>>
>> A correction: Nginx stores "raw" h
At 10:03 PM 10/2/2007 +0200, Manlio Perillo wrote:
>Manlio Perillo ha scritto:
> > [...]
> > As an example Nginx stores all the headers in a associative array,
> > where, of course, only the "last seen" headers appears.
> >
>
>A correction: Nginx stores "raw" headers in a list of key/value pairs,
>
Robert Brewer ha scritto:
>
> [...]
> As you note, it's part of the HTTP spec that such headers
> can be combined without changing the semantics. Here's a list of the
> headers that need to be folded:
>
> comma_separated_headers = ['ACCEPT', 'ACCEPT-CHARSET', 'ACCEPT-ENCODING',
> 'ACCEPT-LANG
Phillip J. Eby ha scritto:
> At 09:30 PM 10/2/2007 +0200, Manlio Perillo wrote:
>> The HTTP 1.1 protocol (section 4.2) says that:
>> """Multiple message-header fields with the same field-name MAY be
>> present in a message if and only if the entire field-value for that
>> header field is defined as
Manlio Perillo ha scritto:
> [...]
> As an example Nginx stores all the headers in a associative array,
> where, of course, only the "last seen" headers appears.
>
A correction: Nginx stores "raw" headers in a list of key/value pairs,
and not in an associative array.
This means that when I ite
Manlio Perillo wrote:
> The HTTP 1.1 protocol (section 4.2) says that:
> """Multiple message-header fields with the same field-name MAY be
> present in a message if and only if the entire field-value for that
> header field is defined as a comma-separated list [i.e., #(values)]."""
>
> This can
On Tue, Oct 02, 2007 at 09:30:46PM +0200, Manlio Perillo wrote:
> The HTTP 1.1 protocol (section 4.2) says that:
> """Multiple message-header fields with the same field-name MAY be
> present in a message if and only if the entire field-value for that
> header field is defined as a comma-separated
At 05:47 PM 10/1/2007 +0200, Manlio Perillo wrote:
>Hi, I have another question with error handling.
>
>The WSGI spec only says that applications *must* not generate hop-by-hop
>headers, but says nothing on how a WSGI server should handle them.
>
>In the previous version of nginx mod_wsgi I just ig
At 09:30 PM 10/2/2007 +0200, Manlio Perillo wrote:
>The HTTP 1.1 protocol (section 4.2) says that:
>"""Multiple message-header fields with the same field-name MAY be
>present in a message if and only if the entire field-value for that
>header field is defined as a comma-separated list [i.e., #(valu
The HTTP 1.1 protocol (section 4.2) says that:
"""Multiple message-header fields with the same field-name MAY be
present in a message if and only if the entire field-value for that
header field is defined as a comma-separated list [i.e., #(values)]."""
This can happen, as an example, with the Co
12 matches
Mail list logo
