debug verbosity helped me see in cache.log that it was trying port 80 on squid 2 and when i set squid 2 http_port to 8003 and squid 1 httpd_accel_port to 8003 things started working......
----- Original Message ----- From: "mlister" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 3:38 PM Subject: [squid-users] dual accellerators; navigation woes > I've setup two accelerators in the following configuration. > client->SQUID1->SQUID2->webserver > below is the configurations (away from default) and the > navigations I am testing. I need the second navigation > listed for SQUID 1 to work. > > SQUID 1 > ------- > http_port 80 > httpd_accel_host 10.10.1.73 > httpd_accel_port 80 > http_access allow all > > http://10.10.1.77/OA_HTML/US/ICXINDEX.htm ~~works > http://10.10.1.77/OA_HTML/jtflogin.jsp ~~doesn't work > > SQUID 2 > ------- > http_port 80 > httpd_accel_host webserver.domain.org > httpd_accel_port 8003 > http_access allow all > > http://10.10.1.73/OA_HTML/US/ICXINDEX.htm ~~works > http://10.10.1.73/OA_HTML/jtflogin.jsp ~~works > > squid shows typical "Access control configuration prevents > your request from being allowed at this time. Please contact > your service provider if you feel this is incorrect". > > SQUID 1 access.log shows "1048537841.283 987 10.10.1.92 > TCP_NEGATIVE_HIT/403 1468 GET http://10.10.1.73/OA_HTML/jtflogin.jsp - > NONE/- text/html" > > SQUID 2 doesn't show an entry for this attempt in its log. > > Above 10.10.1.92 is the client pc, 10.10.1.73 is SQUID 2, and again this is > coming from SQUID 1's access log. > all above navigations work when plugging in the real webserver.domain.org > > Any ideas? >
