|
|
How to Migrate from
the Internet Junkbuster
|
|
Internet Junkbuster Compatibility
| |
It's easy to migrate from the
Internet Junkbuster Proxy (from
Junkbusters.com) to the Guidescope service.
All of the features of the Internet Junkbuster are present in the Guidescope service.
This page tells you how to migrate quickly.
It assumes that you are already using the Internet Junkbuster Proxy.
You will find more details about compatibility with the Internet Junkbuster Proxy in our manual page
here. On-line documentation for the
Internet Junkbuster Proxy is available at
www.junkbuster.com.
|
|
Thread Requirements
| |
All versions of Guidescope require thread support. Most modern systems support threads.
If your system doesn't support threads, then the Guidescope software won't run on your system.
This will mostly affect users running older versions of Linux without thread support.
Our Linux X86 binaries are compiled on a Slackware 7.0 system using the C library "libc6" (a.k.a "glibc").
If you are using older libraries on Linux, you will have to upgrade your Linux
installation to use more current C libraries before you can run the Guidescope software.
Windows95/98/ME/NT/2K users are unaffected by this change because Windows95/98/ME/NT/2K supports threads.
| |
Migration steps
|
- Install the Guidescope software following all the
installation instructions.
- Copy your Junkbuster configuration files into the directory where you have installed
the Guidescope software.
- Rename your main configuration file "guide.ini" or, if you prefer, "junkbstr.ini".
- Cookies are not blocked by default unless you have a cookie file. If you don't
have a Junkbuster cookie file and want all cookies to be blocked, then
create an empty file named "cookie.ini" and place it in the directory where you installed
the Guidescope software. It behaves exactly like the cookie file in the Internet
Junkbuster. For simplified instructions on its use see our manual page
here. For more information, see the Internet Junkbuster
Cookie FAQ.
If you already have a "cookiefile" directive in your configuration file, make sure it
names the correct file.
- The "user-agent" in the header is not replaced unless you specifically set the
"user-agent" option in your configuration file. If you want to change or hide your user-agent
name (your reported browser type), set it in your configuration file.
We recommend that you not set the user agent because many
Web sites now present content that is formatted differently depending on your user agent. They do
this to work around browser bugs and differences in browser behavior. Of course, if you want to
hide your user-agent, you can still do so.
- The "referer" in the header is now replaced by the URL of the current request.
This satisfies Web sites that refuse to serve content unless the referrer is their own site, while
still effectively removing the referrer information from the header.
If you want referrer information to be discarded then add a line to your configuration file:
referrer !
This will discard the referrer information just like the original Internet Junkbuster.
- The Guidescope software allows users to change its debug or
proxy-chaining settings by simply requesting a special URL
(http://set.debug/ and http://set.proxy/ respectively).
This is convenient in a single-user configuration but
may be undesirable in a shared-proxy environment. To disable
these features, add these directives to the configuration file:
disable-user-debug-config
disable-user-proxy-config
If these options are set then the debug and proxy settings can
be changed only by editing the appropriate configuration files,
as with the Internet Junkbuster.
More details about compatibility with the Internet Junkbuster Proxy is available
here.
|
|
