mån 2008-02-18 klockan 16:31 -0600 skrev Keith M. Richard: > To try and give a little more data to the original message, here is output > from squidclient: > > [EMAIL PROTECTED] squidclient -r -v -p 8888 -m GET > http://www.my-company.org/randomimages/servlet/org.groupbenefits.portal.RandomImageGenServlet?key=C72J9aHy%2BTw%3D%0D%0A"; > headers: 'GET > http://www.my-company.org/randomimages/servlet/org.groupbenefits.portal.RandomImageGenServlet?key=C72J9aHy%2BTw%3D%0D%0A > HTTP/1.0 > Pragma: no-cache > Accept: */*
> Even though I have told the squidclient to use port 8888 it still goes over > to port 80? No. Squidclient went to the proxy on port 8888, which then went to port 80. > > http_port 80 defaultsite=www.my-company.org > > http_port 192.1.0.59:8888 defaultsite=www.my-company.org I guess you meant to use defaultsite=www.my-company.org:8888 above.. > > https_port 443 cert=/etc/squid/cert/portalcert.pem > > key=/etc/squid/cert/key.pem defaultsite=www.my-company.org > > cache_peer 192.1.0.59 parent 443 0 no-query originserver ssl login=PASS > > name=www.my-company.org > > cache_peer 192.1.0.59 parent 8888 0 no-query originserver You also need a bit of cache_peer_access to select what requests to send where.. Actually you can most likely get rid of the http_port 8888 and just use cache_peer_access to select proper routing of requests. But this requires chaning the web site to use port 80 for the image in the HTML/scripts.. Regards Henirk
signature.asc
Description: Detta är en digitalt signerad meddelandedel
