Article delegate-en/5112 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
[Reference:<_A5111@delegate-en.ML_>]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: DeleGate: HTTP Keep Alive on Client Side
10 Dec 2014 12:39:49 GMT feedback@delegate.org (Yutaka Sato)
The DeleGate Project


Hi Emerson,

In message <_A5111@delegate-en.ML_> on 12/10/14(12:31:11)
you Emerson Gomes <piuiqbdyi-jfbrsz7km5xr.ml@ml.delegate.org> wrote:
 |Hello,
 |
 |I am not being able to make DeleGate use keep alive on client side on a
 |HTTP proxy if HTTP Status from upstream server is "202.Accepted"
 |(Connection: close header is received)
 |
 |This is logged also:
 |HCKA:[0] closed -- s:bad status: -202
 |
 |It will work fine if response from upstream is 200.
 |
 |The Delegate to server keep-alive is also working fine.
 |
 |Is there a way to force delegate to use keep alive in client side even if
 |server HTTP status <> 200?
 
I hope the patch enclosed makes you happy.

 |Thanks in advance,
 |Emerson

Cheers from Japan,
Yutaka
--
  9 9   Yutaka Sato { Do the more with the less -- B. Fuller }
 ( ~ )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan


*** prev/src/http.c	Sun Sep 28 20:05:24 2014
--- ./src/http.c	Wed Dec 10 21:26:02 2014
***************
*** 5948,5953 ****
--- 5948,5954 ----
  		RX_rdHeadTotal = lastRcc;
  		switch( RX_code ){
  		case 200:
+ 		case 202: /* v9.9.14 141210b */
  		case 204:
  		case 301:
  		case 302: /* OK and cachable */

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
@_@V