On Mon, Dec 6, 2010 at 11:22 AM, Simon Males <sime(at)sime.net.au> wrote:
> I have just witnessed a Pound read error. The Chrome (8.0.552.215)
> user was being redirected to a HTTPS page.
> Client Error: Error 101 (net::ERR_CONNECTION_RESET): Unknown error.
> Server Error: Dec 6 10:23:21 host pound: (b7a9eb90) error read from
> x.x.x.x: Connection timed out
I am testing Pound 2.4.4 and managed to get another error from Chrome.
Client : Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error.
Server: Dec 8 10:11:26 host pound: (b7a16b90) error read from
x.x.x.x: Connection timed out
A second reload will render the page. It's almost like the pound isn't warm.
Though further digging has found more Chrome related errors.
Loading a static asset (e.g. an image) will successfully download in
Chrome, though 9-10 seconds later (like clockwork) this appears in
Dec 8 12:25:54 host pound: (b79b0b90) error read from x.x.x.x:
Connection timed out
This was consistent on Mac and Linux clients. In tcpdump I can see
pound trying to communicate with the client again. The behavior here
was strictly Chrome specific.