Re: HTTP Server Filtering

Jake Messinger (jake@ams.com)
Wed, 23 Apr 1997 22:40:46 -0500 (CDT)

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.
>
> </chris>
>
> Any chance of those paper cups and string being upgraded to tin cans
> and wire? Or as a coworker has said . . . I've seen better throughput
> from a pair of gorillas and flash cards. -Jon Lewis <jlewis@fdt.net>

but dont you have to tell the web client to look at a different port too?
>

~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Jake Messinger 713-772-6690 jake@ams.com
Advanced Medical Systems, Inc. jake@uh.edu
Houston, Texas http://www.ams.com/~jake
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~

One should not be measured by his/her ascii art ability.