lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV X-URL header field


From: Foteos Macrides
Subject: Re: LYNX-DEV X-URL header field
Date: Tue, 25 Nov 1997 00:52:13 -0500 (EST)

Uzi Paz <address@hidden> wrote:
>I'm not sure that if you post a local (non-public) file, then giving its
>local location is not a privacy problem.

        Yes, I've been thinking about that.  It has been giving the
URL of mailed local files since the original Lynx without anyone as
yet having complained about that, and the user can see the URL even
if it weren't included in the mailing.  It's only a potential problem
when you access local files directly, via the command line startfile,
a 'g'oto entry, or the DIRED_SUPPORT.  Otherwise, it was an HREF in
a text/html document, and is not likely be a "secret".


>Is there any case where both Content-Location and X-URL appear but they
>have different values?

        The X-URL always is what was used to retrieve the document.
The Content-Location will be whatever was received via an http(s)
header, and in theory could be different.  If no Content-Location
header was received by Lynx, then it will be the same as X-URL.
The Content-Base is whatever Lynx used when rendering the document,
which may be one sent by an http(s) server, but that would be replaced
by a BASE element's HREF, if present.  If there was neither a BASE
element nor Content-Base header, but there was a Content-Location
header with and an absolute URL, then that is used as the base and
in turn becomes the Content-Base header Lynx sends.  Otherwise, it
also becomes the same as X-URL.

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================

reply via email to

[Prev in Thread] Current Thread [Next in Thread]