Warning: masking HTTP Headers can cause some web sites to break. Privacy
Shield is intended for advanced users only.
Privacy Shield is an advanced HTTP filtering plug-in for the Internet
Explorer browser. Built with your privacy in mind, Privacy Shield filters
information as it being passed on by your browser, removing or masking
sensitive data when found.
It's an unknown fact that when you surf the web your browser sends out
information about your browser, system and internet connection. This information
is called HTTP Headers that can contain information that is commonly used
by marketers and statistical analysis programs. Privacy Shield can be
configured in the Control Panel to remove / mask several such HTTP Headers:
Accept-Encoding
The Accept-Encoding field can be used to restricts
the content-codings that are acceptable in the response. If an Accept-Encoding
field is present in a request, and if the server cannot send a response
which is acceptable according to the Accept-Encoding header, then the
server SHOULD send an error response with the 406 (Not Acceptable) status
code. If no Accept-Encoding field is present in a request, the server
MAY assume that the client will accept any content coding. In this case,
if "identity" is one of the available content-codings, then the server
SHOULD use the "identity" content-coding, unless it has additional information
that a different content-coding is meaningful to the client.
Accept-Language
The Accept-Language field can be used to restricts the set
of natural languages that are preferred as a response to the request.
If no language- range in the field matches the tag, the language quality
factor assigned is 0. If no Accept-Language header is present in the request,
the server SHOULD assume that all languages are equally acceptable. If
an Accept-Language header is present, then all languages which are assigned
a quality factor greater than 0 are acceptable.
Add Random Header
Sends a random HTTP header to the web server. Validity of
the defined HTTP headers is not checked by the server but does confuse
log analysis, and may cause custom applications to break.
User-Agent
The User-Agent request-header field contains information
about the user agent originating the request. This is for statistical
purposes, the tracing of protocol violations, and automated recognition
of user agents for the sake of tailoring responses to avoid particular
user agent limitations. User agents SHOULD include this field with requests.
The field can contain multiple product tokens and comments identifying
the agent and any subproducts which form a significant part of the user
agent. By convention, the product tokens are listed in order of their
significance for identifying the application.
Referrer Header
The Referer[sic] request-header field allows the client
to specify, for the server's benefit, the address (URI) of the resource
from which the Request-URI was obtained (the "referrer", although
the header field is misspelled.) The Referer request-header allows a server
to generate lists of back-links to resources for interest, logging, optimized
caching, etc. It also allows obsolete or mistyped links to be traced for
maintenance.
Download Foxie 1.1.0 for Windows (1.4 MB)
Search Adobe PDF with Desktop Search
Next
Feature