Hi Willy,
On 20 June 2012 19:44, Willy Tarreau w...@1wt.eu wrote:
Hi Damien,
On Wed, Jun 20, 2012 at 04:19:09PM +0100, Damien Churchill wrote:
I've found another place where the behaviour appears to diverge from
the documentation. At the beginning of section 4 it says that it's
mandatory
Hi List,
We are using HAProxy 1.5-dev11 and have a small issue with it.
Some of our coders use php firebug when they are debugging code. php
firebug puts a lot of stuff in the response headers (X-WF-* headers)
But, it looks like HAProxy blocks responses when the headers are larger
than 8KB.
Hi Sander,
On Thu, Jun 21, 2012 at 02:06:59PM +0200, Sander Klein wrote:
Hi List,
We are using HAProxy 1.5-dev11 and have a small issue with it.
Some of our coders use php firebug when they are debugging code. php
firebug puts a lot of stuff in the response headers (X-WF-* headers)
Hello,
The ices protocol is based on HTTP and is used for online streaming. In the
early days the specification for this protocol was to use
1 GET /serv/login.php?lang=enprofile=2 *ICE*/1.0
2 Host: www.mydomain.com
3 User-agent: my small browser
4 Accept:
Hi Sander,
On Thu, Jun 21, 2012 at 09:06:06PM +0200, Sander Klein wrote:
Hi,
On 21.06.2012 14:17, Willy Tarreau wrote:
Some of our coders use php firebug when they are debugging code. php
firebug puts a lot of stuff in the response headers (X-WF-* headers)
But, it looks like HAProxy blocks
Hello Martin,
On Thu, Jun 21, 2012 at 07:49:13PM -0400, Martin Konecny wrote:
Hello,
The ices protocol is based on HTTP and is used for online streaming. In the
early days the specification for this protocol was to use
1 GET /serv/login.php?lang=enprofile=2 *ICE*/1.0
2
Hi Willy,
I can only answer your question by saying that other clients that use this
protocol but replace ICE/1.0 with HTTP/1.0 have no problem with HAProxy.
It seems that those other clients realized it wasn't a good idea to change
that part for no good reason :).
I thought I had found a
7 matches
Mail list logo
