Mailing List Archive: Issue 587 in cherokee: HTTP reverse proxy keepalive broken

Issue 587 in cherokee: HTTP reverse proxy keepalive broken

Sep 27, 2009, 7:12 AM

Post #1 of 7 (3014 views)

Status: New
Owner: ----

New issue 587 by praseodym: HTTP reverse proxy keepalive broken
http://code.google.com/p/cherokee/issues/detail?id=587

It looks like the HTTP reverse proxy keepalive function is broken. I'm
running a comet-enabled
application within Jetty, proxied by Cherokee. With keepalive enabled,
connections are dropped
randomly causing the application to hang randomly. With keepalive disabled,
the problems
disappear and the application runs fine.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Issue 587 in cherokee: HTTP reverse proxy keepalive broken [ In reply to ]

codesite-noreply at google

Sep 27, 2009, 7:16 AM

Post #2 of 7 (2958 views)

Permalink

Updates:
Labels: Type-Defect Priority-Medium OpSys-All Component-Logic Usability

Comment #1 on issue 587 by ste...@konink.de: HTTP reverse proxy keepalive
broken
http://code.google.com/p/cherokee/issues/detail?id=587

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Issue 587 in cherokee: HTTP reverse proxy keepalive broken [ In reply to ]

codesite-noreply at google

Sep 29, 2009, 12:39 AM

Post #3 of 7 (2950 views)

Permalink

Comment #2 on issue 587 by alobbs: HTTP reverse proxy keepalive broken
http://code.google.com/p/cherokee/issues/detail?id=587

When you said you disabled keep-alive, did you mean on Cherokee?

I'm just guessing here, but.. did you try to increase the global keep-alive
limit
value in Cherokee? The browser-web server connection might be closed by the
server
when it detects a timeout (and the reverse proxy might have had nothing to
do with it).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Issue 587 in cherokee: HTTP reverse proxy keepalive broken [ In reply to ]

codesite-noreply at google

Sep 29, 2009, 12:52 AM

Post #4 of 7 (2937 views)

Permalink

Comment #3 on issue 587 by ste...@konink.de: HTTP reverse proxy keepalive
broken
http://code.google.com/p/cherokee/issues/detail?id=587

In this case ment the keep-alive connection to the backend server.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Issue 587 in cherokee: HTTP reverse proxy keepalive broken [ In reply to ]

codesite-noreply at google

Sep 29, 2009, 4:20 AM

Post #5 of 7 (2949 views)

Permalink

Comment #4 on issue 587 by praseodym: HTTP reverse proxy keepalive broken
http://code.google.com/p/cherokee/issues/detail?id=587

I disabled the backend keepalive function; after this things started to
work normally. I'll check if increasing the
global limit helps (would actually be nice if there would be a separate
backend keepalive limit)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Re: Issue 587 in cherokee: HTTP reverse proxy keepalive broken [ In reply to ]

cherokee at googlecode

May 18, 2011, 9:55 AM

Post #6 of 7 (2555 views)

Permalink

Comment #5 on issue 587 by alobbs: HTTP reverse proxy keepalive broken
http://code.google.com/p/cherokee/issues/detail?id=587

Many changes have been made since this bug was logged almost three years
ago. I do not believe the bug exists any longer, although I'd like to
ensure it before closing the bug. Is it working with on Cherokee 1.2.x?

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Re: Issue 587 in cherokee: HTTP reverse proxy keepalive broken [ In reply to ]

cherokee at googlecode

Jun 11, 2012, 7:19 AM

Post #7 of 7 (2346 views)

Permalink

Updates:
Status: Fixed

Comment #6 on issue 587 by ste...@konink.de: HTTP reverse proxy keepalive
broken
http://code.google.com/p/cherokee/issues/detail?id=587

I think we can safely close this bug, please reopen it if you can still
reproduce it with the most recent stable code.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev