Get one strange error that I never seen before Total events captured on [05/Jan/2017:09:13:56.054] : 12
[05/Jan/2017:09:09:06.594] frontend http-in (#3): invalid request
backend (#-1), server (#-1), event #11
src 70.192.67.217:3224, session #243701, session flags 0x0080
HTTP msg
Yes, please apply Willy's patch to the 1.7.1 release and tell us what happens. Everything looks good. No errors. About 1.6.11. It was in the first days of December. May be I've mixed up something.I can test again tomorrow if you want It was 1.6.10. I think I've made some mistakes in paths so
Hi Willy,
Am 03.01.2017 um 21:10 schrieb Willy Tarreau:
It was not dropped since the server SACKed it (but until it's within the
window the stack is free to change its mind). In fact following a TCP
stream in wireshark never gives any useful information. You *always* need
the absolute
Hi guys,
On Tue, Jan 03, 2017 at 09:10:21PM +0100, Willy Tarreau wrote:
> However when looking at the error capture, the request is correct. But as
> you can see, it's reported as wrong from offset 1453, hence one byte past
> the end of the first segment. Thus I suspect that we have something
On Thu, Dec 29, 2016 at 08:31:51AM +0100, Willy Tarreau wrote:
> I'm puzzled. I'm going to check the error path in the code as it's something
> I've never ever seen yet! Thus I suspect a regression in 1.7 compared to 1.6.
One of the report mentions 1.6.10 there, it's even more troubling.
I'm
Hello,
Am 28.12.2016 um 11:38 schrieb c...@xmonetize.net:
Tcpdump shows normal http requests(attached)
Ok, I've looked through those traces and a lot of those HTTP 400 errors
come from Browser pre-connect feature - which is not a problem.
However, the TCP session 410 (tcp.stream eq 410)
6 matches
Mail list logo
