On Mon, Mar 31, 2008 at 1:40 PM, Tony Sidaway <[EMAIL PROTECTED]> wrote:
> Thanks for a very informative analysis.
>
> Of course this whole problem only cropped up because we Schemers like
> to build up lists by consing new elements to the front. I would
> probably have included a "reverse" in
Thanks for a very informative analysis.
Of course this whole problem only cropped up because we Schemers like
to build up lists by consing new elements to the front. I would
probably have included a "reverse" in the result of the let loop
without thinking, but unless you have reason to suspect th
On Fri, Mar 28, 2008 at 8:31 PM, Drake Wilson <[EMAIL PROTECTED]> wrote:
> [RFC excerpts snipped]
> My interpretation of this is:
>
> - Forwarders are not permitted to rearrange multiple Set-Cookie
> headers. HTTP client and server libraries have the same
> constraint.
>
> - Origin se
Quoth Graham Fawcett <[EMAIL PROTECTED]>, on 2008-03-28 09:59:16 -0400:
> RFC2109 allows for multiple Set-Cookies, but it also
> warns that "an intervening gateway could fold multiple such headers
> into a single header". Since "folding" is undefined, there's no way
> the origin server can guarante
On Thu, Mar 27, 2008 at 9:07 PM, Tony Sidaway <[EMAIL PROTECTED]> wrote:
> Using http.egg to write a bot that has to login to a ubb forum, I
> discovered that the cookie processing order of that egg resulted in
> login failure. When I tweaked http:read-request-attributes to
> reverse the order
