This is a brief description of what the default HTTP header filters provided with the Proxomitron do. Note that like the web filters, new header filters are always being added and improved, this list might not be exhaustive. Also most filters include (in) or (out) in the name. Not too surprisingly an (in) filter would normally be made active by checking the IN column in the header filter list while for an (out) filter you'd check the OUT column. Also, a very few filters may be apply to both.
Note: Many of the header filters are rather technical in nature (much more so than the web filters) and several are provided as examples only. To help make things easier, the filters most people may find useful are highlighted in red. These are the ones you'll probably want to concentrate on. Meanwhile, those more esoteric (i.e. useless) filters are lowlighted in Gray.
Accept-encoding: Allow webpage encoding (out)
This filter tells a web server it's OK to use "Content Encoding" with web pages it sends to Proxomitron. This is can be used to compress pages so they transfer faster, however not all browser or web servers support it. Proxomitron can now decompress common content-encodings internally (using zlib.dll) and filter the results. The pages are then sent to the browser in normal un-encoded form. You can use this filter to add compression capability even if your browser doesn't normally support it. Using this filter can also help ensure the pages are compressed using one of the methods Proxomitron understands.
Accept-encoding: Prevent webpage encoding (out)
This filter is the opposite of the one above. It tells a web server not to use content encoded (compressed) pages. In the past this was necessary in order for the page to be filtered. However, you shouldn't need to use it anymore unless you want to disable compression for some reason.
Authorization: Example password entry (out)
This filter is an example of how to automatically send a password protected web pages. Use the MIME encode/decode option available by highlighting and right-clicking over the filter's replacement text to encode or decode the username:password pair. (note: this only works for pages that use standard HTTP passwords - some pages may use custom CGI scripts instead).
Cache-Control: always cache (in)
This is one of several header filters that can stop a web site from not allowing their pages to be stored in your browser's cache. Using these filters can prevent wasted page reloads and speed surfing, but on the down-side may also mean you may have to hit your browser's reload button to see if a page has been recently updated.
Connection: Close all connections (In+Out)
Enabling this under both IN and OUT will prevent Proxomitron from re-using HTTP connections. Normally you wouldn't want this unless you're having some specific problems with persistent connections.
Content-Type: Fix MIME types (In)
Sometimes a web server will send items with an incorrect "Content-Type" header. This may prevent Proxomitron or your browser from correctly dealing with the files. This filter uses the MIME List.txt file to fix many commonly misconfigured types. It's a good one to use most all the time.
Content-Type: Show contents of .pac files (in)
Content-Type: View RealAudio links (in)
Another rather "special case" filter. This one will show the contents of RealAudio links (which are often pointers to other URLs with the actual video or audio file). Sometimes this can be useful to see, but most of the time you won't want this filter.
Content-Type: character set filter (in)
This filter is an example of how to control the character set a web page may try and make your browser use. Use it only if a page is misconfigured or forcing your browser to use an inappropriate character set. By duplicating the filter and using it's URL match you can automatically fix problem pages you may visit often.
Cookie: Fake a cookie (out)
This cookie filter changes any cookie your browser sends out to say only "Monster" - kind of fun but probably not too useful. However you can use it as a basic example of custom cookie modification.
Cookie: Kill a cookie (out)
Kills any outgoing cookies that may already be set in your browser before they reach the web server. If enabled, it will check the CookieList blockfile for sites you want to allow cookies through.
Expires: always cache (in)
This is another of several header filters that can stop a web site from not allowing their pages to be stored in your browser's cache. Using these filters can prevent wasted page reloads and speed surfing, but on the down-side may also mean you may have to hit your browser's reload button to see if a page has been recently updated.
This is an example of how to add a "Forwarded:" header filter as some non anonymous proxy servers may do. Only ours can send anything you like (instead of your computers IP address). Generally its not of much use though since it can't change headers added "after the fact" by an external proxy server.
If-Modified-Since: Always reload pages (Out)
Can be enabled to force a web server to always send a page even if it hasn't changed from the one in your browser's cache. Normally it's probably not something you'll want to do.
Removes the date a web page was last modified from the server's reply. Probably not a filter you'll want to use regularly, but can force IE to recognize a new page (sometimes IE will actually ignore a page it's been sent and used its cached copy instead - this is useless since the bandwidth has already been used).
Pragma: Don't force reloads (out)
Your browser sends a "Pragma: no-cache" header when it wants to reload a page and make sure it gets a fresh copy. You can use this to remove these headers, but unless you have a good reason, you probably should leave them alone.
Proxy-Authorization: Send password to proxy server (out)
Similar to the "Authorization:" header filter above, but this is an example of how to send a password to a proxy server. Note: in such cases it's usually easier to use the advanced proxy settings instead.
Referer: Hide where we've been (Out)
The referrer normally tells a website the URL of the last page you visited. This may be something you prefer them not to know - especially if your visiting the page by clicking a link in from your email or a private message board. Much sensitive information can be leaked this way. By default Proxomitron will send the web pages own URL instead. This looks more or less normal to the server, but doesn't reveal any information. I recommend using this if you're security conscious.
Set-cookie: Make all cookies session only (in)
When enabled this will try and turn any "permanent" cookie into a "temporary" (or session-only) cookie. A temporary cookie is not stored on your computer's hard drive and will disappear the next time you start your browser. Making them temporary renders them "mostly harmless" while stopping the web server from complaining that you won't accept its cookies. Either use this filter or the "Never accept cookies" filter below (for stricter control), but don't use both.
This filter also uses the "CookieList" for those sites where you may actually want a permanent cookie (for example, sites that use automatic logins or preference settings).
Set-cookie: Never accept cookies (In)
When enabled this filter will only allow cookies from sites in your "CookieList". Use it for stricter cookie management than the "Make cookies session only" filter above.
URL-Killer: kill-a-URL (out)
This filter will completely block connections to any host listed in your the "AdList" blockfile. This insures that listed sites are never contacted and can't track you via web bugs, cookies, and such even if they slip past the banner filters. You can disable this filter for less aggressive blocking, but in most cases it's better to just remove a blocked site from the list.
URL: Alias Redirector (Out)
This filter allows you to quickly jump to URLs in the "URL Alias List" file. Using it you can set up "Aliases" for sites you visit often. Just type a period in front of your alias in the browser's location bar. For example, you can type ".sd" to jump to "www.slashdot.org". It's easy to add your own aliases - just edit the URL Alias List text file to see how.
URL: Enable Netscape Keywords (Out)
Both Netscape and IE will automatically jump to a likely site if you type a single word in the location bar. To do this they call a special search engine with a database of common names. Unfortunately this feature often doesn't work well through a proxy. Using this filter allows Proxomitron to transparently emulate this feature.
URL: Un-Prefixer (Out)
This is similar to the "URL unprefixer" web filter but works at the header level using redirects. In most cases you'll probably want to stick with the Web filter version, but this is provided as an example.
The User-Agent filters normally tells a website information about your web browser and operating system. Use these filters to tell it something different, and pretend to be using any browser or OS you choose. Proxomitron now includes several sample user-agents filters you can choose from (Including it's own somewhat infamous "SpaceBison"), or you can create additional UA's of your own. Just be sure to enable only one at a time. Also be aware some sites may complain *cough*hotmail*cough* if they don't think you're using a browser they "approve" of. Then again, other sites when faced with an off-the-wall UA may avoid sending "rich media" ads or other annoyances.
WWW-Authenticate: filter out password requests (in)
Will stop web page password requests from being sent to your browser. However, it will NOT let you into a password protected site! It just stops your browser from pestering you about it.
Similar to the "Forwarded:" filter, this is an example of how to add the "X-Forwarded-For:" header filter as some non anonymous proxy servers may use. This will not remove such a header however (since the proxy adds it after it's already left Proxomitron).
Return to main index