[squid-users] Request: help with testing of authentication

Wanted:

People who can help testing Squid.

As some of you may have noticed the list of patches to Squid-2.5.STABLE1
is increasing thanks to many good bug or misfeature reports. Many thanks
to all users who have provided really usable bug report far beyond "it
does not work".

However, the developers goal is to also have the issues with
authentication not being usable in other directives than http_access
fixed in 2.5.STABLE2.

Robert has kindly developed a patch which hopefully fixes the core of
these issues, allowing proxy_auth or other authentication related
directives to be used in other access lists, but due to limited access
to lab equipment and time help is needed to test what works and what
not.

Requirements:
* You have time to spend on testing and analysing any problems found.
* You are somewhat experienced in compiling, patching and running
Squid-2.5.
* You have a lab environment where can run Squid with authentication,
both Basic and NTLM (only one is required, both preferred)
* Your lab environment includes one or more web servers where you have
access to the access log to see which IP address the request came from
(optional, but required for testing of tcp_outgoing_address)
* You know how to get a stacktrace from a crashing Squid (see squid FAQ
on reporting bugs if not)

If you feel that you are in a situation where you can help with this
testing then
1. grab a current Squid-2.5.STABLE nightly snapshot release
2. plus the patch currently found in bug entry 448
<url:http://www.squid-cache.org/bugs/show_bug.cgi?id=448>
3. patch squid with the above patch and install as usual
[note: if the patch has been stroken out then it has been applied to the
current snapshot release. In such case see the bug notes for further
instructions]
4. configure Basic and NTLM authentication schemes
5. test basic functionality in http_access
6. when you have authentication working proper in http_access, continue
by testing other access type directives as listed below
7. Please follow up into bug entry 448 referenced above on your findings
of what works and not.

Needed to work for 2.5.STABLE2:
  http_reply_access
  delay_access
  tcp_outgoing_address

Wanted:
  tcp_outgoing_tos
  redirector_access

Would be nice:
  no_cache
  miss_access
  never_direct
  always_direct
  broken_posts

Note that for tests to be valid authentication needs to be enforced in
http_access first, but it is also interesting to have tested what
happens when it is not (the access line should in such cases be
ignored).

If you find any other issues in this or other testing of Squid, please
register them as separate bugs in our bug tracking database
<url:http://www.squid-cache.org/bugs/>.

If you can help with such testing efforts on a regular basis please
contact squid-dev@squid-cache.org. It happens quite often that Squid
developers need help testing or verifying their changes.

Regards
The Squid HTTP Proxy development team
Received on Fri Jan 10 2003 - 15:42:31 MST