Daniel Appleby wrote:
Did it continue to spam the logs after you blocked it off with an acl?
-Daniel
Any URL blocked explicitly with a Squid ACL will be logged as a 403.
To not log these requests as being blocked...
1) allow them without authentication
2) block them before they hit Squid
or
3) modify the source code
One other thing you could try would be to set an explicit ACL matching
that URL, and set a deny_info that redirects requests to something else
(a local repository with the file, a non-existent server, a server that
returns a 404, etc.). Any of those methods might slow the Java update
service down (or satisfy it).
Chris
