[squid-users] Identifying the source of Invalid-request (squid 3) -> error:transaction-end-before-headers (Squid 4)
jester at optimera.us
Thu Nov 3 14:13:36 UTC 2016
That is how I felt about it, since nothing in the changelog indicated anything that would impact that. I'll switch back to the old version tonight, maybe the client traffic that was inducing the entries that isn't trying anymore? I don't have a good answer, I'll try the old version tomorrow and see if the invalid-request lines come back.
> -----Original Message-----
> From: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] On
> Behalf Of Amos Jeffries
> Sent: Wednesday, November 2, 2016 6:58 PM
> To: squid-users at lists.squid-cache.org
> Subject: Re: [squid-users] Identifying the source of Invalid-request (squid 3) -
> > error:transaction-end-before-headers (Squid 4)
> On 3/11/2016 2:47 a.m., Jester Purtteman wrote:
> > Hello Alex et al.
> > So, life got on top of me instead, and I haven't had time to do much
> testing.... Well, not totally true, did some testing but haven't discovered
> anything useful. But, from the "new and interesting" department, I updated
> 3.5 build r14102, and I am not seeing any of the 'invalid-request' lines
> anymore. Don't know what to make of that, but could be, problem solved.
> Interesting. Nothing changed between 14098 (3.5.22 release) and 14102
> relevant to connections. Just build fixes and documentation.
> squid-users mailing list
> squid-users at lists.squid-cache.org
More information about the squid-users