Re: Socket transfer from Apache httpd to a non-httpd process
Hi Suyambu, Take a look at the src for the following module: http://httpd.apache.org/docs/trunk/mod/mod_proxy_fdpass.html Regards, Henrik On Wed, 2012-08-01 at 09:04 +0200, suyambu wrote: Hi Henrik, I am trying some experiments in httpd2.2. I want to transfer the client socket to another process. From this thread i saw u implemented that feature, Can you provide suggestion how to implement that. Its urgent . It will be very helpful for me. Thanks in advance. Regards, Suyambu -- View this message in context: http://apache-http-server.18135.n6.nabble.com/Socket-transfer-from-Apache-httpd-to-a-non-httpd-process-tp4829341p4999088.html Sent from the Apache HTTP Server - Module Writers mailing list archive at Nabble.com.
Re: Socket transfer from Apache httpd to a non-httpd process for https connections
Hi Ray, I'm using a slightly modified version of http://httpd.apache.org/docs/2.3/mod/mod_proxy_fdpass.html Regards, Henrik On Fri, 2012-01-20 at 17:12 +0100, Ray Morris wrote: I'm using a httpd module that does a socket transfer from the httpd process to another non-httpd process that is running on the same system. Can you post or send that code or a link to it?
Re: Socket transfer from Apache httpd to a non-httpd process for https connections
I'm using a httpd module that does a socket transfer from the httpd process to another non-httpd process that is running on the same system. Can you post or send that code or a link to it? -- Ray Morris supp...@bettercgi.com Strongbox - The next generation in site security: http://www.bettercgi.com/strongbox/ Throttlebox - Intelligent Bandwidth Control http://www.bettercgi.com/throttlebox/ Strongbox / Throttlebox affiliate program: http://www.bettercgi.com/affiliates/user/register.php On Fri, 20 Jan 2012 10:54:35 +0100 Henrik Strand henrik.str...@axis.com wrote: Hi, I'm using a httpd module that does a socket transfer from the httpd process to another non-httpd process that is running on the same system. This works but currently only for http connections. I would now like to get it working for https connections as well. My thoughts are that httpd in some way should re-connect to itself from the https connections to port 80 and transfer the http connection to my other process while keeping the https connection alive and inside the httpd context. Does httpd support this out-of-the-box or can this be done with a specific httpd module or with some httpd.conf magic? Or do I need to write a module myself that does this? Thanks in advance. Best Regards, Henrik
Re: Socket transfer from Apache httpd to a non-httpd process
Hi Eric, Great! Looks like just the thing I'm looking for. Thanks! Best regards, Henrik On Thu, 2011-06-16 at 17:46 +0200, Eric Covener wrote: 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 process finish the connection.
Re: Socket transfer from Apache httpd to a non-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 closed and I'm not able to write to the socket anymore. You probably want to dup() the socket fd before passing it to the external process.
Re: Socket transfer from Apache httpd to a non-httpd process
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 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 closed and I'm not able to write to the socket anymore. You probably want to dup() the socket fd before passing it to the external process.
Re: Socket transfer from Apache httpd to a non-httpd process
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 process finish the connection.
