Now in English:
My reading of WSGI was that implementations should already be folding
multi-line headers.
Cheers,
On 2006/09/09, at 5:18 PM, Mark Nottingham wrote:
> My reading o WSGI was that multi-line headers should already be
> folding multi-line headers. If that's the case, what's the p
My reading o WSGI was that multi-line headers should already be
folding multi-line headers. If that's the case, what's the problem?
Cheers,
On 2006/09/08, at 2:02 PM, Robert Brewer wrote:
> PEP 333 says:
>
> "Each header_value must not include any control characters,
> including carriage re
On Sep 9, 2006, at 1:51 AM, Robert Brewer wrote:
> James Y Knight wrote:
> > I don't see what's wrong with encoding with the 75-char
> > word-limit, separating "words" by spaces, *without* newlines.
> > If the server feels like folding a long line into two, it
> > can do so, but it's perfectly wi
Title: RE: [Web-SIG] WSGI and long response header values
James Y Knight wrote:
> I don't see what's wrong with encoding with the 75-char
> word-limit, separating "words" by spaces, *without* newlines.
> If the server feels like folding a long line into
Title: RE: [Web-SIG] WSGI and long response header values
James Y Knight wrote:
> On Sep 8, 2006, at 7:22 PM, Robert Brewer wrote:
> > Bah. I knew I forgot a constraint in there (the strings
> > have to be encoded by the app). Personally, I think the
> > "separat
On Sep 8, 2006, at 7:22 PM, Robert Brewer wrote:
> Bah. I knew I forgot a constraint in there (the strings have to be
> encoded by the app). Personally, I think the "separate-by-spaces"
> cure is worse than the disease. I also finally found the only other
> discussion of this issue [1] and .
At 06:31 PM 9/8/2006 -0500, Ian Bicking wrote:
>Robert Brewer wrote:
> > PEP 333 says:
> >
> > "Each header_value must not include any control characters, including
> > carriage returns or linefeeds, either embedded or at the end. (These
> > requirements are to minimize the complexity of any parsin
Robert Brewer wrote:
> PEP 333 says:
>
> "Each header_value must not include any control characters, including
> carriage returns or linefeeds, either embedded or at the end. (These
> requirements are to minimize the complexity of any parsing that must be
> performed by servers, gateways, and i
Title: RE: [Web-SIG] WSGI and long response header values
Phillip J. Eby wrote:
> Robert Brewer wrote:
> >So in my reading of HTTP, some code somewhere should introduce newlines in
> >longish, encoded response header values. I see three options:
> >
> > 1.
At 02:02 PM 9/8/2006 -0700, Robert Brewer wrote:
>PEP 333 says:
>
>"Each header_value must not include any control characters, including
>carriage returns or linefeeds, either embedded or at the end. (These
>requirements are to minimize the complexity of any parsing that must be
>performed by s
Title: WSGI and long response header values
PEP 333 says:
"Each header_value must not include any control characters, including carriage returns or linefeeds, either embedded or at the end. (These requirements are to minimize the complexity of any parsing that must be performed by servers, g
11 matches
Mail list logo
