<div dir="ltr">Can you try something: add 'set bereq.http.connection = "Close"; ' at the beginning of vcl_backend_fetch and see if that helps?</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>-- <br></div>Guillaume Quintard<br></div></div></div>
<br><div class="gmail_quote">On Thu, Mar 30, 2017 at 1:04 PM, Hazar Güney <span dir="ltr"><<a href="mailto:hazarguney@gmail.com" target="_blank">hazarguney@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">MaxKeepAliveRequests 20<br><div>KeepAliveTimeout 2</div><div><br></div><div>Version is "4.1.3 revision 5e3b6d2". We have also seen "<span style="font-size:12.8px">straight insufficient bytes" error with POST requests to a specific php script hosted by another backend and fixed it by using "pipe" instead of "pass" but this specific backend gives "http first read error: EOF" error. Another example from today:</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">* << BeReq >> 126635444 </span></div><div><span style="font-size:12.8px">- Begin bereq 126635443 fetch</span></div><div><span style="font-size:12.8px">- Timestamp Start: 1490870598.921499 0.000000 0.000000</span></div><span class=""><div><span style="font-size:12.8px">- BereqMethod GET</span></div><div><span style="font-size:12.8px">- BereqURL XXXX</span></div><div><span style="font-size:12.8px">- BereqProtocol HTTP/1.1</span></div></span><div><span style="font-size:12.8px">- BereqHeader Host: XXXX</span></div><div><span style="font-size:12.8px">- BereqHeader User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36</span></div><div><span style="font-size:12.8px">- BereqHeader Accept: image/webp,image/*,*/*;q=0.8</span></div><div><span style="font-size:12.8px">- BereqHeader Referer: XXXX</span></div><div><span style="font-size:12.8px">- BereqHeader Accept-Language: tr-TR,tr;q=0.8,en-US;q=0.6,en;<wbr>q=0.4</span></div><div><span style="font-size:12.8px">- BereqHeader RIP: XXXX</span></div><div><span style="font-size:12.8px">- BereqHeader X-Forwarded-For: XXXX</span></div><div><span style="font-size:12.8px">- BereqHeader Accept-Encoding: gzip</span></div><div><span style="font-size:12.8px">- BereqHeader X-Varnish: 126635444</span></div><span class=""><div><span style="font-size:12.8px">- VCL_call BACKEND_FETCH</span></div><div><span style="font-size:12.8px">- VCL_return fetch</span></div></span><div><span style="font-size:12.8px">- BackendOpen 35 reload_2017-03-20T11:32:44.st2 10.35.78.11 80 172.17.0.2 48896</span></div><div><span style="font-size:12.8px">- BackendStart 10.35.78.11 80</span></div><div><span style="font-size:12.8px">- Timestamp Bereq: 1490870598.922050 0.000552 0.000552</span></div><span class=""><div><span style="font-size:12.8px"><b>- FetchError http first read error: EOF</b></span></div></span><div><span style="font-size:12.8px">- BackendClose 35 reload_2017-03-20T11:32:44.st2</span></div><div><span style="font-size:12.8px">- Timestamp Beresp: 1490870598.922622 0.001124 0.000572</span></div><div><span style="font-size:12.8px">- Timestamp Error: 1490870598.922627 0.001129 0.000005</span></div><span class=""><div><span style="font-size:12.8px">- BerespProtocol HTTP/1.1</span></div><div><span style="font-size:12.8px">- BerespStatus 503</span></div><div><span style="font-size:12.8px">- BerespReason Service Unavailable</span></div><div><span style="font-size:12.8px">- BerespReason Backend fetch failed</span></div></span><div><span style="font-size:12.8px">- BerespHeader Date: Thu, 30 Mar 2017 10:43:18 GMT</span></div><span class=""><div><span style="font-size:12.8px">- BerespHeader Server: Varnish</span></div><div><span style="font-size:12.8px">- VCL_call BACKEND_ERROR</span></div><div><span style="font-size:12.8px">- BereqHeader X-Varnish-Backend-5xx: 1</span></div><div><span style="font-size:12.8px">- VCL_return retry</span></div></span><div><span style="font-size:12.8px">- Timestamp Retry: 1490870598.922657 0.001159 0.000030</span></div><div><span style="font-size:12.8px">- Link bereq 126832283 retry</span></div><div><span style="font-size:12.8px">- End </span><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 12:03 PM, Mattias Geniar <span dir="ltr"><<a href="mailto:mattias@nucleus.be" target="_blank">mattias@nucleus.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> Backend is Apache.<br>
<br>
In older Varnish versions, you could sometimes see a similar error;<br>
<br>
> 11 FetchError c straight insufficient bytes<br>
<br>
The error message you’re seeing might be related, as it mentions the EOF.<br>
<br>
This happens when the backend sends a Content-Length header that doesn’t match the _actual_ content length it’s sending. In Apache, this was commonly caused by a mod_deflate misconfiguration.<br>
<br>
For testing, could you try disabling Gzip either in your backend or strip the Accept-Encoding header in Varnish to force a plain text response?<br>
<span class="m_-8440447935089024071HOEnZb"><font color="#888888"><br>
Mattias<br>
<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>