[Top][All Lists]

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

Re: [Chicken-users] Hang problem with the http egg.

From: Peter Bex
Subject: Re: [Chicken-users] Hang problem with the http egg.
Date: Wed, 12 Mar 2008 18:40:56 +0100
User-agent: Mutt/

On Wed, Mar 12, 2008 at 09:01:29AM -0700, Robin Lee Powell wrote:
> > There isn't one.
> > 
> > Oh, wait, there *IS*.  How did I miss that?  Yeesh.
> The answer is that the http egg eats it somehow; here's the headers
> output from http:
> headers: ((content-type . text/plain) (expires . Thu, 01 Jan 1970
> 00:00:00 GMT) (pragma . no-cache) (cache-control . no-cache)
> (connection . close) (server . Jetty/5.1.x (Windows XP/5.1 x86
> java/1.5.0_06) (date . Wed, 12 Mar 2008 15:41:57 GMT)).
> I'm looking at the http egg code, and I don't see how that's
> happening, but my *guess* is that it's dropping whatever the last
> header is on the floor, because curl says that header is last:

In your tcpdump output I don't see the header at all.  If there's no
content-length, it will wait for the other side to send an EOF.
If there's none, it will wait forever.

> The other possibility is that that header is failing the regex, but
> a quick test with egrep shows that that doesn't seem to be the case.
> HTTP/1.1 200 OK
> Date: Wed, 12 Mar 2008 15:57:16 GMT
> Server: Jetty/5.1.x (Windows XP/5.1 x86 java/1.5.0_06
> Cache-Control: no-cache
> Pragma: no-cache
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Type: text/plain
> Content-Length: 9

Where's this header coming from?  Perhaps CURL is sending a request that
looks different to the server, causing it to send a different response?

"The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music."
                                                        -- Donald Knuth

Attachment: pgpVf_8QUfgPE.pgp
Description: PGP signature

reply via email to

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