Re: SOLVED! (Was: 400 error on cookie string)

On Thu, Jan 05, 2017 at 10:24:30PM +0300, Aleksey Gordeev wrote: > Hi, I'm "cas". My Name is Aleksey Gordeev. I was using my company email. > Please set me as a reporter. Perfect, thanks for clearing this up. You did a great job and I'm often embarrassed not to name good reporters (and many want

Re: SOLVED! (Was: 400 error on cookie string)

Hi Willy, all, On 17-01-05 20:17:56, Willy Tarreau wrote: > "cas", if you want to be credited as a reporter of the issue, you > need to raise your hand very quickly now, because once the patch is > merged it will be too late. His name is Aleksey Gordeev, see 9060941483541...@web3g.yandex.ru,

Re: SOLVED! (Was: 400 error on cookie string)

Hi, I'm "cas". My Name is Aleksey Gordeev. I was using my company email. Please set me as a reporter. 2017-01-05 22:17 GMT+03:00 Willy Tarreau : > Small update on this, Axel Reinhold faced an apparently different > issue on an SVN server until we noticed the requests were sent in >

Re: SOLVED! (Was: 400 error on cookie string)

Small update on this, Axel Reinhold faced an apparently different issue on an SVN server until we noticed the requests were sent in small chunks cut before the CRLF and experiencing the same problem. He could confirm the patch fixes the problem for him as well, so I'm going to merge the patch now.

Re: 400 error on cookie string

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

Re: 400 error on cookie string

  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

Re: 400 error on cookie string

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

SOLVED! (Was: 400 error on cookie string)

I found it and fixed it! It was me again who added a bug in 1.7 with the optimizations for large headers and large requests. If certain conditions are met, we could read the \r from previous data (as we guessed) and complain that the next byte was not an LF once the remaining part arrived. I'm

Re: 400 error on cookie string

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

Re: 400 error on cookie string

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

Re: 400 error on cookie string

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)