forwarded once Ubuntu updates haproxy package version.
Regards,
Óscar
On Fri, Feb 24, 2023 at 4:13 PM Óscar Frías Barranco
wrote:
> Hello Willy.
>
> Thank you very much for the detailed answer. I have reported this in
> Jetty issue tracker, I hope they can support this use c
t; On Fri, Feb 24, 2023 at 02:19:30PM +0100, Óscar Frías Barranco wrote:
> > Hello
> >
> > I am using haproxy 2.4.18 with a frontend configured with alpn
> h2,http/1.1
> >
> > The problem that I am facing is that if I add "proto h2" to the backends,
> >
Hello
I am using haproxy 2.4.18 with a frontend configured with alpn h2,http/1.1
The problem that I am facing is that if I add "proto h2" to the backends,
when a remote client connects to the frontend using HTTP 1.1, the request
is sent to the backend server without copying the "Host" header to t
can include in the documentation of
"http-pretend-keepalive" something like this:
"This option is recommended when using http-server-close for backends
running: Tomcat 5.5.28 or below, Tomcat 6.0.26 or below, or Jetty.".
2010/4/1 Óscar Frías Barranco
> I have "forw
On Wed, Mar 31, 2010 at 07:15:34PM +0200, Óscar Frías Barranco wrote:
> > I have been looking at Tomcat source code and apparently it looks like
> there
> > is an easy fix.
>
> That's good news !
>
> > Here is the class where the logic is implemented:
> >
&
On Thu, Apr 1, 2010 at 11:32, Patrik Nilsson wrote:
> Hi,
>
> 2010/3/30 Óscar Frías Barranco :
> <...>
> > It seems to me that when http-server-close option is enabled, haproxy
> > replaces the original request header "Connection: Keep-Alive" by
>
> > In any case, if you consider that this Tomcat behavior is buggy we could
> > report the issue to Tomcat team and maybe they can fix it.
>
> If we're certain that it's just "Connection: close" which automatically
> disables use of chunked encoding, then yes it's a buggy behaviour and maybe
> the
> > As a quick and dirty test, I've applied the following patch.
> > Note this is maybe not OK for production, it's a first look on the
> problem, so be careful (I only took some minutes on a tomcat server with
> gzip compression, which removes the Content-Length when "Connection: close"
> is provi
On Wed, Mar 31, 2010 at 06:37, Willy Tarreau wrote:
> It says that if a message does not have any content length NOR chunked
> transfer encoding, THEN the only way to detect the end is the close.
> Chunked transfer encoding requires HTTP version 1.1, that's all. There's
> nothing wrong in using c
> I'm also thinking about implementing TPROXY so that I don't have to add
> the headers and modify the webserver logging. Maybe that's an option for
> you, too?
>
> regards,
>
> Craig
>
>
> Am 30.03.2010 23:55, schrieb Óscar Frías Barranco:
> > I a
to
>> Connection: Keep-Alive
>>
>> Netcat received in fact :
>> GET / HTTP/1.1
>> Host: toto
>> Connection: close
>>
>> I don't get it ... HTTP/1.1 says that by default keep-alive is activated
>> on every request unless Connection: close is s
Hello.
I have just read Patrik Nilsson email about http-server-close and Jetty.
Unfortunately I cannot reply to that email because I read it in the archives
and I was not subscribed to the list.
We are facing a very similar problem using Tomcat 6.0.20 in the backend (and
haproxy 1.4.2).
When we
12 matches
Mail list logo
