I'm testing pound to see if it will be useful for
my environment. I compiled pound Version 2.3.2 on
a Linux X86_64 system using this configuration:

LogLevel 5
ListenHTTP
         Address 1.2.3.4
         Port    80
End

Service
         URL     ".*"
         BackEnd
                 Address 1.2.3.5
                 Port    80
         End
End

The backend is the publicfile Web server serving strictly
static content - publicfile is incapable of anything else.
I sometimes see this error in the pound log:

unexpected chunked EOF: Connection timed out

and the client (Firefox) waits for a long time. I
have to restart pound to get it working again.
If I go directly to the publicfile backed, it always
works OK. Any ideas?

Ed

On Tue, 2007-06-26 at 11:24 -0700, Ed Sawicki wrote:[...]

Increase the back-end time-out.[...]

Robert Segall wrote:[...][...][...]

I see that the default timeout is 15 seconds. My backend
is in a test environment now and always responds immediately.
The problem seems to be related to chunked encoding.
publicfile _always_ uses chunked encoding when responding to
a HTTP/1.1 request.

Ed

Robert Segall wrote:[...][...][...]

I _reduced_ the back-end timeout to 2 seconds. This improved
things. Now the browser displays the pages after a 2-second
delay worst case. I still see the

unexpected chunked EOF: Connection timed out

messages in the logs, so I didn't fix anything. I just made it
more tolerable.

Ed

Ed Sawicki wrote:[...][...]
>>> I'm testing pound to see if it will be useful for
>>> my environment. I compiled pound Version 2.3.2 on
>>> a Linux X86_64 system using this configuration:
>>>
>>> LogLevel 5
>>> ListenHTTP
>>>          Address 1.2.3.4
>>>          Port    80
>>> End
>>>
>>> Service
>>>          URL     ".*"
>>>          BackEnd
>>>                  Address 1.2.3.5
>>>                  Port    80
>>>          End
>>> End
>>>
>>> The backend is the publicfile Web server serving strictly
>>> static content - publicfile is incapable of anything else.
>>> I sometimes see this error in the pound log:
>>>
>>> unexpected chunked EOF: Connection timed out
>>>
>>> and the client (Firefox) waits for a long time. I
>>> have to restart pound to get it working again.
>>> If I go directly to the publicfile backed, it always
>>> works OK. Any ideas?[...][...]

I setup two back ends that serve the identical content:

1.publicfile Web server - always returns chunked
   responses for any HTTP/1.1 request.

2.thttpd Web server - always returns a Content-Length:
   header for HTTP/1.1 requests for static content (does
   not use chunked encoding)

When I use the publicfile back end, I frequently see the
above mentioned errors in the pound logs and the browser
user experiences delays.

When I use the thttpd back end, there are no errors and
everything works as expected.

Is there something more I can do to characterize the
problem?

Ed