[SQU] Safe_ports and port 1024

I've been revising some of the acls on our Squid caches and noticed what
seems to be a discrepancy between the range of Safe_ports, which
includes the range 1025-65535 and IANA's list
(http://www.isi.edu/in-notes/iana/assignments/port-numbers), which has
well-known-ports as 0-1023, registered ports 1024-49151 and
dynamic/private ports as 49152-65535.

Is Squid's range intended to match IANA's, and if so, should the range
in Safe_ports not start at 1024 instead of 1025?

The reason I ask is that I had to include an acl to allow access to a
service on port 1024 at archive.stsci.edu, which would not have been
required if Squid had that port as "safe" by default. We're in a cache
hierarchy, so I can't simply change Safe_ports on our cache, because our
parent caches most likely don't allow URLs with port 1024. I also need
to use allow_direct to bypass our parents.

Not a big issue, I know, but maybe one that could be corrected in future
releases?

-- 
David Osborne                         david.osborne@nottingham.ac.uk
Academic Computing Services     phone/voicemail: +44 (0)115 951 3397
The University of Nottingham                fax: +44 (0)115 951 3358
Nottingham NG7 2RD, UK          http://www.nottingham.ac.uk/~cczdao/
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html