That's a security feature. Netscape/Mozilla will never send the referrer
header if the referrer URL is HTTPS and the destination is HTTP.
Likewise, we won't send the header between two different HTTPS servers,
only to URLs on the same server. In general, you shouldn't write
applications that depend on referrer headers, because user agents can
always opt not to send them.
BTW, if you're using NS6.1, I strongly recommend upgrading to 6.2.2.
-Mitch
UAIS wrote:
> Does anyone know of a workaround for retrieving the http_referer header from
> a netscape 6.1 browser over an https connection. The variable gets set over
> standard http connection, but fails over a https connection.
>
> any ideas please reply to this newsgroup or
> [EMAIL PROTECTED]
>
> Thanks
>
>
>
