Re: binding server to already used port 80

Only one program can bind and listen on one port at the same time. If you want to have "special" requests, you need to either configure Apache so it calls your script (via mod_perl or CGI, for exmaple), or you have to write your program so that it sits in front of Apache and forwards all "normal" requests to your program (via HTTP::Proxy for example).

If all you want to do is to listen to the incoming requests, I wrote Sniffer::HTTP which listens to all network traffic and extracts the HTTP requests. So maybe you can tell us more about what you want to do.

Comment on Re: binding server to already used port 80 Download Code

Replies are listed 'Best First'.
Re^2: binding server to already used port 80 by opensourcer (Monk) on Jan 12, 2007 at 09:24 UTC
instead of having a mutiple requests( calling from 1. cli to server 2. calling from web(mod_perl) to server, i would like to have a single interface using port 80, so i can do the webwork as well as cli work using the port 80, the cli request would go to port 80 calling mod_perl and then to server.	[reply]
Re^3: binding server to already used port 80 by Joost (Canon) on Jan 12, 2007 at 14:53 UTC
I'm getting confused. You want a single request to do both HTTP and telnet? "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^4: binding server to already used port 80 by Fletch (Bishop) on Jan 12, 2007 at 15:52 UTC
It's a dessert topping AND a floor wax!	[reply]