My apologies [in part] to Arachne.
The problem was not the :80 in the URL. The problem was that the link
on the page was enclosed in "quotation marks" and those quotes ended up
on the URL line.
One I removed the "quotation marks" at both ends of the URL, it went
through just fine.
So, now the question is "Why can't Arachne ignore the " at the beginning
and end of a URL?
Strange thing is that I've had this problem multiple times, and part of
the time if I hit the 'retry' button often enough everything was OK.
But until yesterday I never even saw the darned " " up there.
Oh well, just another thing to remember.
l.d.
====
On Sat, 20 May 2000 12:40:19 +0300, Sergei Kramar wrote:
> On Sat, 20 May 2000 00:25:51 -0400, L.D. Best wrote:
>> Why on earth can't Arachne handle the fact that DNS sometimes changes a
>> URL to include a port designation? And isn't 80 the normal port one
>> would expect for a top webpage?
> Hi, L.D.
> The only function of a DNS-server is to find the IP-address of a host
> machine by its name. Normally, internet servers (not DNS) use 80 port
> to handle client requests via HTTP protocol. By the other words if you
> point URL http://... your web browser automatically add port number 80
> after servername of your request.
>> Places I want to go I can't get to ... not because of DNS problems but
>> because Arachne absolutely refuses to even contact DNS if port 80 is
>> part of the URL alphanumeric code. :<
> The HTTP syntax of Arachne is (see HELP)
> http://[user:pass@]servername[:port][/doc]
> so could you give an example of improperly handled URL.
> Regards.
> Sergei Kramar
> -- Arachne V1.60, NON-COMMERCIAL copy, http://arachne.cz/
--
-- "I need not like the company I keep, if that company helps me
attain my own personal goals and does me no harm." anon.
--
-- Arachne V1.61, NON-COMMERCIAL copy, http://arachne.cz/
