I just realized that this bug was reported *before* google changed the http handling, so the bug reporter might have been experiencing a different problem. Nevertheless, the problem exists now.
I just realized that this bug was reported *before* google changed the http handling, so the bug reporter might have been experiencing a different problem. Nevertheless, the problem exists now.