1995-12-02 - Re: Barring access to Netscape

Header Data

From: Frank Stuart <fstuart@vetmed.auburn.edu>
To: cypherpunks@toad.com
Message Hash: c311ac20115b002270bcb9d8742b448d706bf7e516318cba7c26463a77be0df4
Message ID: <199512022022.OAA19354@snoopy.vetmed.auburn.edu>
Reply To: N/A
UTC Datetime: 1995-12-02 20:33:47 UTC
Raw Date: Sun, 3 Dec 1995 04:33:47 +0800

Raw message

From: Frank Stuart <fstuart@vetmed.auburn.edu>
Date: Sun, 3 Dec 1995 04:33:47 +0800
To: cypherpunks@toad.com
Subject: Re: Barring access to Netscape
Message-ID: <199512022022.OAA19354@snoopy.vetmed.auburn.edu>
MIME-Version: 1.0
Content-Type: text/plain


>> >Shouldn't be too hard to hack this into Apache.
>
>	Should my commercial release of Apache/SSL include this? ;-)
>(I could make it into a configuration option, so that if the
>User-Agent is Mozilla, it passes Back a Refresh: header with the
>response....)

Well, I think configurable redirects based on User-Agent would be a good
thing.  However, if you don't control the server being used you can still
use client pull to redirect on a page-by-page basis.  I've been made aware
of at least one non-Netscape browser that does client pulls, so checking the
User-Agent would be desirable, but (AFAIK) that isn't possible without
modifying the server, using cgi, or something along those lines.

I've got the perl script to automatically add (and remove) the meta-http lines
to individual pages more or less done, but I won't release it just yet
(if at all).  Jeff Weinstein's promise to make Netscape's GAK policy
publically available is an important step in the right direction.  However,
whatever their policy statement ends up saying, it should be obvious that their
level of commitment to opposing GAK is minimal at best.


                          | (Douglas) Hofstadter's Law:
Frank Stuart              | It always takes longer than you expect, even 
fstuart@vetmed.auburn.edu | when you take into account Hofstadter's Law.





Thread