You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging a Drupal site with XDEBUG, it is common that you might be stepping through code for longer than the Varnish timeout of 60 seconds. It appears that the error page that Varnish renders has the undesirable behavior of automatically retrying the failed request after 5 seconds, leading to an avalanche/snowball of requests queuing up on the backend during an extended debugging session. It would be great if there was a way to opt out of this automatic retry behavior, since this isn't how Pantheon itself behaves during a timeout (thankfully).
For reference, here's what the HTML that's rendered back during a timeout looks like (note the auto-retry via setTimeout()):
When debugging a Drupal site with XDEBUG, it is common that you might be stepping through code for longer than the Varnish timeout of 60 seconds. It appears that the error page that Varnish renders has the undesirable behavior of automatically retrying the failed request after 5 seconds, leading to an avalanche/snowball of requests queuing up on the backend during an extended debugging session. It would be great if there was a way to opt out of this automatic retry behavior, since this isn't how Pantheon itself behaves during a timeout (thankfully).
For reference, here's what the HTML that's rendered back during a timeout looks like (note the auto-retry via
setTimeout()
):The text was updated successfully, but these errors were encountered: