*Hello *
*I am a professional Link builder. I am providing guest posting services. I
have many blogs in different niches. I am sending you some blogs. If you
interested*
URL DA Monthly Visits Alexa rank
https://lifehacker.com/
On Wed, May 07, 2014 at 07:30:43AM +0200, Willy Tarreau wrote:
The strange news: Contrary to your statement, the client connection is
closed after the 1 second timeout. It even logs this. The only thing
that doesn't happen properly is the absence of any response. Just
immediate connection
Hi Patrick, hi Rachel,
so with these two patches applied on top of the previous one, I get the
behaviour that we discussed here.
Specifically, we differentiate client-read timeout, server-write timeouts
and server read timeouts during the data forwarding phase. Also, we disable
server read
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-07 09:45:47 E
*To: *Patrick Hemmer hapr...@stormcloud9.net, Rachel Chavez
rachel.chave...@gmail.com
*CC: *haproxy@formilux.org
*Subject: *Re: please check
Hi Patrick, hi
On Wed, May 07, 2014 at 09:55:35AM -0400, Patrick Hemmer wrote:
Works beautifully. I had created a little test suite to test to test a
bunch of conditions around this, and they all pass.
Wow, impressed with the speed of your test! Thanks!
Will see about throwing this in our development
Hi Patrick, hi Rachel,
I might have fixed half of the issue, I'd like you to test the attached patch.
It ensures that the client-side timeout is only disabled after transmitting
the whole body and not during the transmission. It will report cD in the
flags, but does not affect the status code
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-06 17:41:18 E
*To: *Patrick Hemmer hapr...@stormcloud9.net, Rachel Chavez
rachel.chave...@gmail.com
*CC: *haproxy@formilux.org
*Subject: *Re: please check
Hi Patrick, hi Rachel,
I might have fixed half of the issue, I'd like you to test
Hi Patrick,
On Tue, May 06, 2014 at 07:38:04PM -0400, Patrick Hemmer wrote:
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-06 17:41:18 E
*To: *Patrick Hemmer hapr...@stormcloud9.net, Rachel Chavez
rachel.chave...@gmail.com
*CC: *haproxy@formilux.org
*Subject: *Re: please check
Hi
On Thu, May 01, 2014 at 03:44:46PM -0400, Rachel Chavez wrote:
The problem is:
when client sends a request with incomplete body (it has content-length but
no body) then haproxy returns a 5XX error when it should be a client issue.
It's a bit more complicated than that. When the request body
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 02:02:11 E
*To: *Rachel Chavez rachel.chave...@gmail.com
*CC: *haproxy@formilux.org
*Subject: *Re: please check
On Thu, May 01, 2014 at 03:44:46PM -0400, Rachel Chavez wrote:
The problem is:
when client sends a request with incomplete body
Hi Patrick,
On Fri, May 02, 2014 at 10:57:38AM -0400, Patrick Hemmer wrote:
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 02:02:11 E
*To: *Rachel Chavez rachel.chave...@gmail.com
*CC: *haproxy@formilux.org
*Subject: *Re: please check
On Thu, May 01, 2014 at 03:44:46PM -0400
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 11:15:07 E
*To: *Patrick Hemmer hapr...@stormcloud9.net
*CC: *Rachel Chavez rachel.chave...@gmail.com, haproxy@formilux.org
*Subject: *Re: please check
Hi Patrick,
On Fri, May 02, 2014 at 10:57:38AM -0400, Patrick Hemmer wrote:
*From
On Fri, May 02, 2014 at 12:18:43PM -0400, Patrick Hemmer wrote:
At any moment the server is free to respond yes, but the server cannot
respond *properly* until it gets the complete request.
Yes it can, redirects are the most common anticipated response, as the
result of a POST to a page
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 12:56:16 E
*To: *Patrick Hemmer hapr...@stormcloud9.net
*CC: *Rachel Chavez rachel.chave...@gmail.com, haproxy@formilux.org
*Subject: *Re: please check
On Fri, May 02, 2014 at 12:18:43PM -0400, Patrick Hemmer wrote:
At any moment the server
On Fri, May 02, 2014 at 01:32:30PM -0400, Patrick Hemmer wrote:
This only applies if the Expect: 100-continue was sent. Expect:
100-continue was meant to solve the issue where the client has a large
body, and wants to make sure that the server will accept the body before
sending it (and
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 14:00:24 E
*To: *Patrick Hemmer hapr...@stormcloud9.net
*CC: *Rachel Chavez rachel.chave...@gmail.com, haproxy@formilux.org
*Subject: *Re: please check
On Fri, May 02, 2014 at 01:32:30PM -0400, Patrick Hemmer wrote:
I've set up a test
On Fri, May 02, 2014 at 02:14:41PM -0400, Patrick Hemmer wrote:
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 14:00:24 E
*To: *Patrick Hemmer hapr...@stormcloud9.net
*CC: *Rachel Chavez rachel.chave...@gmail.com, haproxy@formilux.org
*Subject: *Re: please check
On Fri, May 02
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 15:06:13 E
*To: *Patrick Hemmer hapr...@stormcloud9.net
*CC: *Rachel Chavez rachel.chave...@gmail.com, haproxy@formilux.org
*Subject: *Re: please check
On Fri, May
...@gmail.com, haproxy@formilux.org
*Subject: *Re: please check
On Fri, May 02, 2014 at 02:14:41PM -0400, Patrick Hemmer wrote:
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-05-02 14:00:24 E
*To: *Patrick Hemmer hapr...@stormcloud9.net
*CC: *Rachel Chavez rachel.chave...@gmail.com, haproxy
Could someone please tell me if what I did is right?
I posted this fix a while ago and I didn't get a response.
http://marc.info/?l=haproxym=139506908430417w=2
Thank you in advance,
--
Rachel Chavez
Hi,
On Thu, May 01, 2014 at 09:56:01AM -0400, Rachel Chavez wrote:
Could someone please tell me if what I did is right?
I posted this fix a while ago and I didn't get a response.
http://marc.info/?l=haproxym=139506908430417w=2
Thank you in advance,
Could you please first describe the
The problem is:
when client sends a request with incomplete body (it has content-length but
no body) then haproxy returns a 5XX error when it should be a client issue.
In the session.c file starting in 2404 i make sure that if I haven't
received the entire body of the request I continue to wait
22 matches
Mail list logo
