Comment 71 for bug 705312

On 02/28/2012 04:02 AM, Cristian Salamea (Gnuthink) wrote:
> I still can reproduce the bug with 3.1.3 tag from bitbucket and proxy
> configurations recommended here.

This bug is basically an upstream bug that we cannot fix ourselves.

As far as I know there is no 3.1.3 tag yet for CherryPy, they are still waiting
for people to test the 3.1.x branch with older versions of Python.
So I don't know what version of CherryPy you are testing with.
See the bug that Christophe reported on
  https://bitbucket.org/cherrypy/cherrypy/issue/1102/313-release-needed

We have not found any proper workaround for this issue, as there is no browser
hook to detect 408 errors and automatically retry them (and the requests that
are failing are not only Ajax, but resources loaded by the browser itself,
which we cannot catch).
You can try Christophe's branch that attempts to catch errors at Ajax level,
but that does not fix the problem, and does not cover all cases where such a
408 error may be raised by CherryPy, as far as I can tell.

Your best bet at the moment is to follow the workarounds that are mentioned in
the bug description. If you can still reproduce the bug and you are 100% sure
you correctly applied the workarounds from the bug description, you will need
to provide us with detailed steps to reproduce and as much analysis as you can
perform, to see if you are hitting a different bug.

In the mean time, the best way to help is to test the 3.1.x branch of CherryPy
with Python 2.4 or Python 2.5 as requested on the ticket, in order to make
release 3.1.3 a reality:
  https://bitbucket.org/cherrypy/cherrypy/issue/1102/313-release-needed