chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] proposed change to http-client


From: Elf
Subject: Re: [Chicken-users] proposed change to http-client
Date: Wed, 13 Feb 2008 14:51:15 -0800 (PST)


<snip>
OK, since I need partial support for HTTP/1.1,
plase do either the followings:

a) modify http:POST so that "Connection: close" is added
  only if the req is string.

what if i do a protocol-version check before adding the conenction close, so
as to preserve proper behaviour under 1.0 ? ie, connection close will only
be added if there isnt an extant connection header and the version == 1.0.


b) modify http:POST and http:GET so that they never
  care the Connection header.

this would break the default behaviour, and is more of a problem with the
http-client egg as a whole, unfortunately. http:GET and http:PUT dont pay attention to the attributes, on the whole. theyre just simplification wrappers for everything beneath. for what its worth, the is-keep-alive? procedure does proper version checking and only closes on the connection header if its explicitly specified, if the protocol-version is 1.1. so as
long as i fix the above bit (not explicitly adding the close), it will work
as you expect in 1.1


-elf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]