Bug with HTTP-Accelerator

There seems to be a bug in the HTTP accelerator part of squid.

I configured squid as an accelerator for one of our clients. Everything
works ok when it runs on port 80. But when I configure squid to run on port
81 (this is a mission critical system and I can't risk taking the running
one on port 80 down to test a new version), I get:

The requested URL could not be retrieved

_________________________________________________________________

While trying to retrieve the URL: http://194.77.23.9:81/

The following error was encountered:
* DNS name lookup failure

The system returned:
DNS Domain '194.77.23.9:81' is invalid: Host not
found (authoritative).

.........

generated by the squid which should be accelerating the site. This is the
corresponding access.log entry:

194.77.23.25 - - [20/Nov/1996:19:07:45 +0100] "GET http://194.77.23.9:81/"
ERR_DNS_FAIL 876 [%0d%0aHost: 194.77.23.9:81%0d%0aAccept: audio/x-wav,
text/html, text/plain, application/x-wais-source, application/html,
*/*%3bq=0.001%0d%0aAccept-Encoding: gzip, compress%0d%0aAccept-Language:
en%0d%0aPragma: no-cache%0d%0aCache-Control: no-cache%0d%0aUser-Agent:
Lynx/2.6 libwww-FM/2.14%0d%0aFrom: lmb@pointer.in-minden.de%0d%0aForwarded:
by http://pointer.teuto.de:8080/ (Squid/1.1.beta19)%0d%0aForwarded: by
http://proxy.teuto.de:8080/ (Squid/1.1.beta13)%0d%0a%0d%0a] []

It appears that the http-accelerator does a DNS lookup on the Host: header
without stripping the port off. I don't know whether the forwarding proxies
are at fault or whether this is a bug in the accelerator itself, but I do
NOT think that the accelerator should concern itself with the Host: header.

-- 
Lars Marowsky-Bree   Voice: +49-571-63663   PGP-key avail. via server
HomePage: http://www.teuto.de/~lmb/    Mail: lmb@pointer.in-minden.de
PGP-Id: 0xDAB57941 / CF FC 3A F0 86 F1 D3 EB  79 8A CF 75 4F 4C 81 DF
     < to prevent forgery, all email by me is signed with PGP >