2010/8/15 Igor Galić i.ga...@brainsware.org
Hi folks,
In stumbling over this: http://dpaste.de/NFVw/
I put together a quick patch.
HTTP/1.0 defaults to Connection: Close. There's no need to transmit those
bytes when specifying 1.0.
Perhaps the server you're using doesn't handle that
This will be happening this week...
As many know, one thing I've wanted in httpd's proxy for
http is a sort of pre-request ping option (ala what we
have for ajp) and nothing ever worked out fine, for a variety
of reasons.
Anyway, I've gone back to an idea I had a long while ago
and one which ACO and Filip Hanik and I have played
On 16.08.2010 15:41, Jim Jagielski wrote:
As many know, one thing I've wanted in httpd's proxy for
http is a sort of pre-request ping option (ala what we
have for ajp) and nothing ever worked out fine, for a variety
of reasons.
Anyway, I've gone back to an idea I had a long while ago
and one
-Original Message-
From: Rainer Jung
Sent: Montag, 16. August 2010 16:40
To: dev@httpd.apache.org
Subject: Re: trunk ping for http proxy
On 16.08.2010 15:41, Jim Jagielski wrote:
As many know, one thing I've wanted in httpd's proxy for
http is a sort of pre-request ping
On Aug 16, 2010, at 10:56 AM, Plüm, Rüdiger, VF-Group wrote:
This basicly sums up the downsides of this approach I see as well.
IMHO to avoid a spec violation we can only add the Expect header to
requests with request bodies. OTOH these requests hurt most when they
fail as we cannot sent
On Mon, Aug 16, 2010 at 8:30 AM, Jim Jagielski j...@jagunet.com wrote:
On Aug 16, 2010, at 10:56 AM, Plüm, Rüdiger, VF-Group wrote:
This basicly sums up the downsides of this approach I see as well.
IMHO to avoid a spec violation we can only add the Expect header to
requests with request
On Aug 16, 2010, at 1:42 PM, Paul Querna wrote:
On Mon, Aug 16, 2010 at 8:30 AM, Jim Jagielski j...@jagunet.com wrote:
On Aug 16, 2010, at 10:56 AM, Plüm, Rüdiger, VF-Group wrote:
This basicly sums up the downsides of this approach I see as well.
IMHO to avoid a spec violation we can
Note that it is an option, not a default setting. The problem with
the heartbeat bit which Red Hat/JBoss use is the unstandardized
proprietary protocol required (http://jboss.org/mod_cluster) with
separate logic to manage it.
The problem with the status url is that it doesn't accomplish the same
On Mon, Aug 16, 2010 at 2:28 PM, Andrew Oliver acoli...@gmail.com wrote:
Note that it is an option, not a default setting. The problem with
the heartbeat bit which Red Hat/JBoss use is the unstandardized
proprietary protocol required (http://jboss.org/mod_cluster) with
separate logic to
10 matches
Mail list logo
