you'll get the source code for some nice hostile applets
Let's have a look at all the applets we are loading "without knowing it" just by browsing around:
Open your c:\NAVIGA~1.CACHE directory and, using your hexeditor,
have a look at all the *.class files you loaded. Navigator, unfortunately, gives names without meaning to its cache files (using the "real" names
of the files should be one of the top priority improvements for the next version), but you'll find the applets names (among many other information)
inside the code.
When the netscape prompt to accept a cookie appears it often gives the value Apache = nnnnnnn there
are two possible reasons: Apache webservers will automatically set a cookie everytime a person goes there, it's to do
hit counts & accounting. The other is a bug related to earlier versions of Apache where the cookie string is incorrectly
terminated resulting in a cookie value that looks like s=2398709123948701.
there is a patch at Apache's website to fix this.
Where does the cookie go after it is sent back to the server
and how do you read it is another matter: It doesn't really get sent back to the server. It gets sent to he server when the browser makes a request for a page. So
you have to serve your page from a CGI which recieves the cookie along with the page request then generates a custom
page based upon the cookie.
And let's not forget:
Through cookies a browser can be tracked over multiple sites, therefore a
cookie can be used to "register" that you have been to a site, or group of sites X number of times
Good news for the war against Micro$oft!
(I am currently working on it :-)
Another difference between Navigator and Explorer is in the cookie handling category: If you set a cookie in Netscape that is
empty it will be empty, In Explorer it will not change e.g. Set-Cookie myCookie=; expires=Wednesday, 09-Nov-99
23:12:40 GMT... etc. Navigator will say the cookie is "" Explorer will say the cookie is the value that it was set to before
the above Set-Cookie