Re: HTTP Server Filtering

Stephen Fisher (lithium@cia-g.com)
Wed, 23 Apr 1997 23:06:19 -0600 (MDT)

This is one of those problems which there is no full fix for. Like users
defeating idle timers (RFE: Livingston see below!).. But anything helps
deter the user and it is just easier to do it on another service.

RFE: Livingston I would **love** to see a way to add a filter with a
dynamic source or dest. address which you can list things like tcp port
25, 110, icmp, udp blah.. etc.. and apply it to dial-up users <It would
really help for it to be able to use ChoiceNet with it> so those services
do NOT reset the idle timer).

On Wed, 23 Apr 1997, Christopher Hicks wrote:

> On Wed, 23 Apr 1997, Stephen Zedalis wrote:
> > On Wed, 23 Apr 1997, James Moriartey wrote:
> > >Is it possible to create a filter to allow a user to browse
> > >and deny the user to run a HTTP server ?
> >
> > sure, allow tcp port 80 out and deny it coming in.
>
> You can run the web server on virtually any port without difficulty.
> Restricting port 80 just begins a shell game. The user puts it on port
> 81, you restrict port 81, he puts it on 82. Etc.