You need to give Squid read access to the nat device, or else it cannot
find the real destination address of the requested resource.
This will make a difference for old clients not sending Host headers.
-- Henrik Nordstrom Squid hacker Ferry Yanuar wrote: > > Hi all, > I got these messages in my cache.log: > 2000/12/02 12:45:57| parseHttpRequest: NAT open failed: (13) Permission > denied > 2000/12/02 12:45:57| clientReadRequest: FD 94 Invalid Request > 2000/12/02 12:46:48| parseHttpRequest: NAT open failed: (13) Permission > denied > 2000/12/02 12:46:48| clientReadRequest: FD 24 Invalid Request > > Should I worry with these message? How to solve the problem? > FYI I use 2.3S4 as WCCP, FreeBSD 4.0-RELEASE, and I've done the step like > in http://www.squid-cache.org/Doc/FAQ/FAQ-17.html#ss17.10 > Please, what am I missing? > > -- > To unsubscribe, see http://www.squid-cache.org/mailing-lists.html -- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Sat Dec 16 2000 - 09:20:38 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:56:59 MST