[Top][All Lists]

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

Re: lynx-dev Re: Unsupported URL scheme

From: Leonid Pauzner
Subject: Re: lynx-dev Re: Unsupported URL scheme
Date: Sat, 12 Feb 2000 13:30:02 +0300 (MSK)

12-Feb-2000 04:54 Natasha Live wrote:
> Interesting one that i've just spoted.

> Just tried to download a cert advisory using lynx.

> <URL:>
> I tried to download a file called: CA-95:06.satan
> and i get the answer Unsupport URL scheme!

> This works with either <ENTER> or D.

> I would assume that it's reading the CA-95: as the start of the URL instead
> of it being ftp://..../CA-95:....

11-Feb-2000 23:11 Michael Warner wrote:

>       [concerning ftp'ing through a proxy]

This is the case when we have the following html:
<base href="ftp://...";>
<a href="CA-95:06.satan">the link</a>

and lynx trying to qualify CA-95 as a scheme prefix first.
Perhaps is_url() could be made stricter, e.g. search for ://
when this isn't lynx private page (like LYNXHIST:)

>> The proxy sticks in a lot of other junk, too, that until now
>> I was blaming on the ftp servers. ftp_proxy has now been duly
>> commented out in my lynx.cfg, and my world is a little brighter
>> place.
>> Anybody know if that's configurable in the proxy?  If it is, I
>> might be able to convince the local sys-admin to do something
>> about it.  Somehow I doubt that un-escaping those colons
>> qualifies as "best practice".

> Never mind.  The proxy isn't intended for ftp, anyway, according
> to the "auto-config" file you give netscape to tell it what to
> do about proxying.  I guess I should've figured out that it
> didn't make too much sense going through a caching proxy for ftp,
> anyway.  Not too many repeat requests for a given file, I don't
> imagine.

> Netscape doesn't seem to have any qualms about un-escaped colons
> in the URL's, though.  Escapes them internally, maybe?

> --
> Michael Warner
> <address@hidden>

reply via email to

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