Re: [users@httpd] PORT questions]

[Chris Pilson <Ch...@NAU.EDU>]

Well ... I'd love to, but what I'm really building is a stateful packet
filter on 80.  And ... well, I guess that I COULD pick up nasties after
they hit the Apache server ... but I'd rather get to them before, and drop
the packet.

I know you can do this other ways (e.g. at the router), but I want a TON
of flexability, such that I can arbitrarily do things like, say, if the
client sends a /GET/index-forbidden.html request, then the packet is
dumped.

C


On Sun, 5 Jan 2003, Jurgen wrote:

> Date: Sun, 05 Jan 2003 21:04:50 -0500
> From: Jurgen <ap...@squarehosting.com>
> Reply-To: users@httpd.apache.org
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] PORT questions
>
> Hi,
>
> to connect to port 8000 on apache as client you will have to use a regular socket, which will not necessarily be on port 8000. Only the port it will connect to will be port 8000. So you could still listen to with the same application to port 8000 and you wouldn't need port 8001.
> If you connect with the Java program to port 8000 on the server you will get an OutputStream and an InputStream which will receive the reply. If you changed the TCP packages coming from the apache server they will not reach your application. Also, to be receiver at port 8001 you need to establish a tcp connection there as well. If you could modify the resulting package so that a Java DatagramSocket can accept it you could have some success, but I don't know how hard that is. You might have data losses that way though.
>
> Why don't you just use one connection where your Java program is the client and Apache is the server?
>
> Jurgen
>
>
> On Sun, 05 Jan 2003 17:57:58 -0700 (MST)
> Chris Pilson <Ch...@NAU.EDU> wrote:
>
> > Here's what's going on:
> >
> > all I want my software to do is act as a sort of PAT.  The problem is, it
> > can't hook into a port already taken by a listener - this is why I can't
> > just sling this whole thing on port 8000 or whatever.  I want apache to
> > LISTEN on port 8000 (I've got my SW to dump 80 -> 8000), and RESPOND on
> > port 8001, which I have not been able to do yet.
> >
> > I'm using JAVA to do this, and opening up a Listener and ServerSocket
> > object (2 in total).  Below is a map of "the big picture".
> >
> > 	WORLD		MY S/W		APACHE
> > 	=====		======		======
> >
> > 	---->		80--->8000	8000
> > 	80		80<---8001	<---
> >
> > I'm sorry that I'm being so vague here ... I'm looking to use this for my
> > own ends and may end up releasing this, if it's useful - and, of course,
> > if I can get it working!
> >
> > Chris
> >
> >
> > On Sun, 5 Jan 2003, Rich Bowen wrote:
> >
> > > Date: Sun, 05 Jan 2003 18:43:04 -0500 (EST)
> > > From: Rich Bowen <rb...@rcbowen.com>
> > > Reply-To: users@httpd.apache.org
> > > To: users@httpd.apache.org
> > > Subject: Re: [users@httpd] PORT questions
> > >
> > > On Sun, 5 Jan 2003, Chris Pilson wrote:
> > >
> > > > Here's the situation:  I have an apache server <up and running> that I'd
> > > > like to LISTEN to port 8000 and POST <respond> on port 80.  I've looked
> > > > through the FAQs, archives, and documentation and I've never seen anything
> > > > that would let me split the port number that it listens and responds on.
> > > >
> > > > If anyone out there has any ideas, I'm open to them.  This is also my
> > > > server, so I have root.
> > >
> > > If the client connects to port 8000, it will expect the response to come
> > > back on that same connection. If you respond on some other port, then
> > > the client is going to miss the response. So I guess the real question
> > > here is, what problem are you trying to solve with this? Perhaps there's
> > > some other way to get at the solution.
> > >
> > > --
> > > Rich Bowen - rbowen@rcbowen.com
> > > ReefKnot - http://www.reefknot.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > The official User-To-User support forum of the Apache HTTP Server Project.
> > > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > >    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> > > For additional commands, e-mail: users-help@httpd.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org