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/
