[erlang-questions] making http client close connections

[Oscar Hellström]

Hi Joel,

What I meant was to send the Connection: close in the *headers* of the *request*... That signals that the *client* isn't prepared to continue to use the connection after the request/response.

To make it a bit more clear, you could read this:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.10

IIRC inets will notice this, and will close the connection. Otherwise, have you tried to use {version, "HTTP/1.1"} as on HTTPOption?

Best regards

----- "Joel Reymont" <joelr1@REDACTED> wrote:

> On Jun 9, 2009, at 6:43 PM, Oscar Hellström wrote:
> 
> > The client can also send the Connection: close header....
> 
> 
> I cannot send anything from the client since at this point in time I'm
>  
> reading from a keep-alive connection. Actually, I have already read  
> everything I needed and just want to close the socket ... and I
> can't!
> 
> ---
> Mac hacker with a performance bent
> http://www.linkedin.com/in/joelreymont

-- 
Oscar Hellström, oscar@REDACTED
Phone:  +44 (0)798 45 44 773
Mobile: +44 (0)207 65 50 337
Web:    http://www.erlang-consulting.com