David Combs asked... | |What in the world could possibly make the "http://"; prefix |*keep things from working*? | |I'm sure I'll learn something from the answer!
It didn't - you misread things. *All* of the initially given domains/URLs were wrong. Adding http:// simply returned a different (more useful) error message. I've left the rest of the text below so you can see what I'm talking about. [When he says "correct address without http://"; he's contrasting to the original post, with its incorrect addresses, not to the correct address with http:// .] -Miles | |On Wed, Mar 06, 2002 at 08:26:24AM -0500, Ismael Cordeiro wrote: |> On Wed, 6 Mar 2002, David Combs wrote: |> |> > These three urls: |> > |> > www.worldwarIIIreport.com |> > |> > www.worldwariiireport.com |> > |> > http://www.worldwariiireport.com |> > |> > The first two give me something like "badly formed address". |> > |> > The third merely gives something like "site unavailable" (it flashes so |> > fast I can't grab it with mouse-area, to use here). |> > |> > Any idea *what* is "wrong" with those first two? |> > |> > Oh, here's which lynx I'm using: |> > |> > Lynx 2.8.4rel.1 (17 Jul 2001) ([1]latest release) |> |> That address doesn't exist. That's why Lynx says "Unable to connect to |> remote host". The correct one is <http://www.worldwar3report.com>. About |> your first two tries, it's better to turn trace on and see what is |> happening. Anyway, if you use the correct address without "http://"; - |> www.worldwar3report.com - Lynx connects correctly. |> | |What in the world could possibly make the "http://"; prefix |*keep things from working*? | |I'm sure I'll learn something from the answer! | |David | | |; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED] | ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
