Cyril, thanks! It's surprising for me actually - to accept request & log
error simultaneously :)
Btw, I've reconfigured my service to use TCP frontend/backend, so there are
no errors anymore.
PS. Lukas, thanks also! RFC3986 was very helpful - our backend team agreed
to fix the application.
On We
> Le 22/12/2014 19:00, Lukas Tribus a écrit :
>>> OK, got it.
>>>
>>> What should I do with HAProxy to handle with them? (option
>>> accept-invalid-http-request is set already)
>>
>> You can't. HAproxy will not support those URI's.
>>
>> accept-invalid-http-request allows a limited set of forbidden
Hi Juriy and Lukas,
while scrolling into the code, I hit a part of code which reminded me
this thread.
Le 22/12/2014 19:00, Lukas Tribus a écrit :
OK, got it.
What should I do with HAProxy to handle with them? (option
accept-invalid-http-request is set already)
You can't. HAproxy will not
> OK, got it.
>
> What should I do with HAProxy to handle with them? (option
> accept-invalid-http-request is set already)
You can't. HAproxy will not support those URI's.
accept-invalid-http-request allows a limited set of forbidden
chars, but not the ones you are using (> 127/0x7f ASCII).
You
OK, got it.
What should I do with HAProxy to handle with them? (option
accept-invalid-http-request is set already)
On Mon, Dec 22, 2014 at 8:10 PM, Lukas Tribus wrote:
> > Hi,
> >
> > could anyone explain what is wrong with following HTTP-request? Nginx
> > (btw) is working fine.
>
> The conten
> Hi,
>
> could anyone explain what is wrong with following HTTP-request? Nginx
> (btw) is working fine.
The content of objectKey (everything after "objectKey=").
Lukas
Hi,
could anyone explain what is wrong with following HTTP-request? Nginx (btw)
is working fine.
--
[22/Dec/2014:16:33:11.765] frontend https_frontend_ssl_terminate (#3):
invalid request
backend (#-1), server (#-1), event #7
src :49803, session #24184, session flags 0x008
7 matches
Mail list logo
