On Thu, 25 Mar 2010 19:46:09 -0000, Bryce Harrington <email address hidden> wrote:
> Since I get back html error pages in the emails I assume these are
> errors on the launchpad side and not just network flakiness.
The incomplete read is probably the appserver you are talking to
breaking the connection.
The 502 and 503 are likely to be served by the machines in front of the
LP code (HAProxy and Apache?) when they can't proxy your request.
> Is that
> an accurate assumption? I mean, if I'm the only person seeing these
> issues maybe I should be looking for a faulty router or something?
You are not the only person to see them.
Using the network is never going to be reliable. The libarary should
retry transient errors, and should have an API that encourages the user
to consider this and code to expect it.
On Thu, 25 Mar 2010 19:46:09 -0000, Bryce Harrington <email address hidden> wrote:
> Since I get back html error pages in the emails I assume these are
> errors on the launchpad side and not just network flakiness.
The incomplete read is probably the appserver you are talking to
breaking the connection.
The 502 and 503 are likely to be served by the machines in front of the
LP code (HAProxy and Apache?) when they can't proxy your request.
> Is that
> an accurate assumption? I mean, if I'm the only person seeing these
> issues maybe I should be looking for a faulty router or something?
You are not the only person to see them.
Using the network is never going to be reliable. The libarary should
retry transient errors, and should have an API that encourages the user
to consider this and code to expect it.
Thanks,
James