Hi,
I need to transfer the socket descriptor for a client
connection from the Apache httpd process to a non-httpd process running
on the same system as Apache httpd, thus transferring the server
response responsibility from Apache httpd to the non-httpd process
(i.e., the Apache httpd process
On Thu, Jun 16, 2011 at 10:32, Henrik Strand henrik.str...@axis.com wrote:
I've tried writing data to the socket directly after my non-httpd daemon
process receives the socket descriptor and this results in that the
client receives this data. However, very shortly afterwards the
connections is
Hi Ben,
I've tried that but with no success. The problem (i.e., that the
connection is closed) still remains.
Best Regards,
Henrik
On Thu, 2011-06-16 at 13:44 +0200, Ben Noordhuis wrote:
On Thu, Jun 16, 2011 at 10:32, Henrik Strand henrik.str...@axis.com wrote:
I've tried writing data to the
On Thu, Jun 16, 2011 at 10:57 AM, Henrik Strand henrik.str...@axis.com wrote:
Hi Ben,
I've tried that but with no success. The problem (i.e., that the
connection is closed) still remains.
Check out mod_proxy_fdpass in trunk, which replaces the socket httpd
is using and lets the external
On Thu, Jun 16, 2011 at 11:57 AM, Joe Lewis jle...@silverhawk.net wrote:
On Thu, 2011-06-16 at 17:46 +0200, Sorin Manolache wrote:
Hello,
I have a content generator that sets a cookie on a domain. I know the
cookie name and the domain name, they never change. However the cookie
value
On Thu, 2011-06-16 at 12:32 -0400, Shawn Ligocki wrote:
On Thu, Jun 16, 2011 at 11:57 AM, Joe Lewis jle...@silverhawk.net wrote:
On Thu, 2011-06-16 at 17:46 +0200, Sorin Manolache wrote:
Can I get this response just by changing the configuration of apache?
Header edit
On Thu, Jun 16, 2011 at 18:41, Joe Lewis jle...@silverhawk.net wrote:
On Thu, 2011-06-16 at 12:32 -0400, Shawn Ligocki wrote:
On Thu, Jun 16, 2011 at 11:57 AM, Joe Lewis jle...@silverhawk.net wrote:
On Thu, 2011-06-16 at 17:46 +0200, Sorin Manolache wrote:
Can I get this response
On Thu, 2011-06-16 at 18:57 +0200, Sorin Manolache wrote:
On Thu, Jun 16, 2011 at 18:41, Joe Lewis jle...@silverhawk.net wrote:
On Thu, 2011-06-16 at 12:32 -0400, Shawn Ligocki wrote:
On Thu, Jun 16, 2011 at 11:57 AM, Joe Lewis jle...@silverhawk.net wrote:
On Thu, 2011-06-16 at 17:46
On 15 Jun 2011, at 23:01, Paul Querna wrote:
I think we have all joked on and off about 3.0 for... well about 8 years now.
I think we are nearing the point we might actually need to be serious about
it.
…
If we don't, I'm sure others in the web server market will continue to gain
market
-Original Message-
From: Joe Schaefer [mailto:joe_schae...@yahoo.com]
Sent: Donnerstag, 16. Juni 2011 01:44
To: dev@httpd.apache.org
Subject: Re: 3.0, the 2011 thread.
+1 amen to reliability coming first. We run all kinds of
awful code in production at the ASF, and httpd's
On Thu, 16 Jun 2011, Graham Leggett wrote:
On 16 Jun 2011, at 12:01 AM, Paul Querna wrote:
The problem is our process model, and our module APIs.
Apache httpd has always had at it's heart the ability to be practically
extensible, while remaining reliable, and I think we should continue to
Paul Querna [mailto:p...@querna.org] sent on Thursday, June 16, 2011 6:02 AM
I think we have all joked on and off about 3.0 for... well about 8 years now.
...
The problem is our process model, and our module APIs.
The Event MPM was a valiant effort in some ways, but mod_ssl and other
On Wed, Jun 15, 2011 at 5:09 PM, Akins, Brian brian.ak...@turner.com wrote:
On 6/15/11 6:26 PM, HyperHacker hyperhac...@gmail.com wrote:
=
I'd been looking forward to mod_lua for a while now expecting it to
work similarly to PHP (handle requests, send output without having to
worry about how
On Thu, 2011-06-16 at 17:46 +0200, Sorin Manolache wrote:
Hello,
I have a content generator that sets a cookie on a domain. I know the
cookie name and the domain name, they never change. However the cookie
value and expiration time vary. I would like to add the cookie with
same name and
On 6/16/2011 4:18 AM, bswen wrote:
I think the only major problem of httpd is its one thread per connection
I/O model. It's an inherently unscalable design. Httpd-3.0 will be
meaningless if it keeps on this i/o design.
That is no longer its design; it is now one thread per request.
On Thursday 16 June 2011, William A. Rowe Jr. wrote:
On 6/16/2011 4:18 AM, bswen wrote:
I think the only major problem of httpd is its one thread per
connection I/O model. It's an inherently unscalable design.
Httpd-3.0 will be meaningless if it keeps on this i/o design.
That is no
16 matches
Mail list logo
