Cullen Programming

JAVA Internet Proxy Server


HTTP Facility Users Guide


Conventional Protocol Setting Defaults:

HTTP    80

HTTP server and proxy protocol by convention use port 80 for listening for requests.
This is the default setting.
Should you wish to change this due to a conflict with some other product you may. We suggest adding some multiple of 1000, such as 1080, 2080, etc.

Next, you must then configure each network computer's browser to talk to this port assignment. See "Connection" information in Netscape, Mozilla, FireFox or Internet Explorer.

Below is a sample display of the HTTP Daemon settings. Here you can select the listening IP address for browser traffic, disable HTTP protocol, and optionally filter some annoying traffic.

Web Site Blocking
Select with your mouse, any line in the Event Logging display that specifies an HTTP GET type command.  Then select the DENY WEBSITE ACCESS from the VIEW pulldown.  The line will be parsed for the website that you want blocked and be listed in the prohibited website list.  It becomes in force when you depress the APPLY button.

Optionally, you can create a list of prohibited websites by using any text editor to make a list file named "url.psdata" that contains on each line the website address to which you wish to prohibit access.

example:
www.sexparty.com
www.manboylove.com
www.lesbians.com

After saving the file in the product logging directory, simply hit the Apply Button on PServer. You and your users are now immediately protected.

To remove or re-allow access to a previously blocked website simply perform the same steps you would to block the site with the exception of using the ALLOW WEBSITE ACCESS button from the VIEW pulldown.

Filtration
Should you press the "Filtration" button you will see the panel below overlay the Daemon panel. This feature allows you to suppress browsers on your internal LAN from performing a number of GET requests that may contain advertisments and promotions.

The radio button labelled "PopUp Filter" will scan for and suppress any JAVASCRIPT "window.open" commands that are detected in the incoming HTTP stream.

The first column of checkboxes, "qualifiers" will suppress any HTTP GET request that contains a subdirectory matching the filter name (or its plural).

ie.  Selecting "ad.doubleclick.net" will suppress a GET requests like:

GET http://www.cnn.com/ad.doubleclick.net/sell_this/magazine.gif
GET http://www.cnn.com/ad.doubleclick.nets/sell_this/magazine.gif

because the qualifier of "ad.doubleclick.net" appears as a subdirectory of the request.

The second column of checkboxes, "strings" will suppress any HTTP GET request that contains a matching set of characters that compose the filter name (or its plural).

ie.  Selecting "pop_under" will suppress a GET requests like:

GET http://www.cnn.com/pop_under/sell_this/magazine.gif
GET http://www.cnn.com/pop_under/services/subsciption/pic.gif

because the character string of "promo" appears withing the request.

The third column of checkboxes, "other" will suppress incoming and/or outgoing Cookies. contains a matching set of characters that compose the filter name (or its plural). Selection the "CookiesOut" option will suppress the "Cookie:" header field in the HTTP GET request. Selection the "CookiesIn" option will remove the "Cookie-sent:" information from inbound Server response headers.



Please note that your browser's behaviour may change and the display will have missing information fields due to the filtration. Cookie suppression and javascript disablement may render some sites unusable in that they may rely on these techniques to function properly. Some sites may require the permission and ability to store and retrieve "cookies" on your computer for the proper operation of a session with their website. Others may require popups for useful content such as forms, license agreements and userid/password information.


[Return to User Guide Table of Contents]

[Return to Index]

[Return to Cullen Programming Home Page]