"http first read error: EOF" errors from WordPress backend
guillaume at varnish-software.com
Wed Apr 12 11:00:50 CEST 2017
Can you try and report? It may be a bug on either side, deactivating
temporarily could confirm that it's indeed a gzip problem.
On Fri, Mar 31, 2017 at 2:31 PM, Hazar Güney <hazarguney at gmail.com> wrote:
> But "Content-Length" header is not available at all. I'm afraid we cannot
> keep gzip disabled even if it solves the issue, Varnish has to be able to
> handle gzipped inputs from the backend.
> On Fri, Mar 31, 2017 at 11:11 AM, Mattias Geniar <mattias at nucleus.be>
>> > - FetchError http first read error: EOF
>> > - BackendClose 21 reload_2017-03-21T100643.default
>> > - Timestamp Beresp: 1490916389.664967 60.000557 60.000114
>> > - Timestamp Error: 1490916389.664978 60.000567 0.000011
>> At the risk of repeating myself: try to disable gzip & any wordpress
>> plugins that might be trying to gzip on their own (aka: output buffering in
>> To me, this seems like Varnish is waiting for the backend to send more
>> data, because it replied with a certain Content-Length header but sent a
>> few bytes less than it advertised, and Varnish is waiting for those missing
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc