On 06/06/2013 02:00 AM, Sean Boran wrote: > I've started getting increasing "zero sized reply" messages in the > browser when visiting sslbump'ed sites again. > A reload in the browser usually works, but its annoying for users. > > Last night I got many many of these while trying to access > https://drupal.org/user/password > In there logs there is not much: > TCP_MISS/502 4600 POST https://drupal.org/user/password - > PINNED/140.211.10.16 text/html > > Are others having such issues, what is current recommendation? I'm > still running trunk from dec with the 19190-001.patch referenced > below. The relevant code has changed a lot since then, hopefully for the better. For example, the "better approach" mentioned in the email below is now implemented. Consider upgrading to v3.3. HTH, Alex. > On 20 December 2012 08:55, Sean Boran <sean@xxxxxxxxx> wrote: >> >> I applied that the first patch a few days back, no complaints so far. >> >> Sean >> >> >> On 13 December 2012 16:14, Alex Rousskov >> <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> wrote: >>> >>> On 12/11/2012 02:40 AM, Sean Boran wrote: >>>> Hi, >>>> >>>> It happens a few times daily that on submitting a login request to >>>> sites like Atlassian confluence (not just at atlassian, but elsewhere >>>> too), or Redmine, that the user gets a screen "The requested URL could >>>> not be retrieved" and with a "zero sized reply". >>>> >>>> It does not happen every time. >>>> If one refreshes the browser it is ok. >>>> If the destination is excluded from SSL interception, it does not >>>> happen. >>> >>> Yes, this is a known issue with bumped requests and persistent >>> connection races. Our patch for this bug is available at >>> http://article.gmane.org/gmane.comp.web.squid.devel/19190 >>> >>> and we are also working on a better approach to address the same bug: >>> http://article.gmane.org/gmane.comp.web.squid.devel/19256 >>> >>> >>> HTH, >>> >>> Alex. >>> >>> >>> >>
