This is a discussion on Re: [squid-users] problem with accelerator and / within the Squid Users forums, part of the Web Server and Related Forums category; --0__=07BBE723DFF7BB9E8f9e8a93df938690918c07BBE723DF F7BB9E Content-type: text/plain; charset=US-ASCII BTW, I currently have apache configured with "UseCanonicalName Off&...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--0__=07BBE723DFF7BB9E8f9e8a93df938690918c07BBE723DF F7BB9E
Content-type: text/plain; charset=US-ASCII BTW, I currently have apache configured with "UseCanonicalName Off" - also tried twiddling the port in the ServerName directive, and switching UseCanonicalName to On, but none of those seemed to make a difference. Brad Brad Horstkotte To: Robert Collins <robertc@squid-cache.org> 09/29/2003 10:30 cc: Squid Users <squid-users@squid-cache.org> AM Subject: Re: [squid-users] problem with accelerator and /(Document link: Brad Horstkotte) Can you be more specific? My site is working fine when accessed directly via Apache, its only after putting the squid acceleration in front of it that the problem appears - as far as I understand the HTTP RFC, my Apache is doing what its supposed to - I requested a directory, it found a matching index file, and passed back a 302 + Location specifying the absolute URL (including port) to the requesting browser. Or is there something I'm missing? Any other ideas? Can someone pass on a working squid acceleration configuration, so I can compare with mine to see what might be different? Thanks - Brad Robert Collins <robertc@squid-ca To: Brad Horstkotte/AFS/CAPITAL@CG che.org> cc: Squid Users <squid-users@squid-cache.org> Subject: Re: [squid-users] problem with accelerator and / 09/27/2003 03:49 PM On Sat, 2003-09-27 at 07:26, Brad_Horstkotte@capgroup.com wrote: > > > Hi, I've installed and configured Squid (NT 2.5 STABLE 3), and have it > "mostly" working - I have squid running on port 3128, and on the same > machine I'm forwarding requests to an Apache 2.0.47 running on port 82. > Fully qualified URLs work fine, but if I hit a folder (like "/"), the > request comes back to the browser via port 82 instead of 3128. The web > server is returning a 302 response along with a "Location: > http://localhost:82/index.htm" header. How can I configure Squid to handle > the Location header properly, so that all requests from the 3128 port come > back via port 3128? This is a problem with your Apache configuration. It needs to tell the browser the correct details: incorrect headers are not the only problem you will be suffering. Rob -- GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>. (See attached file: signature.asc) --0__=07BBE723DFF7BB9E8f9e8a93df938690918c07BBE723DF F7BB9E Content-type: application/octet-stream; name="signature.asc" Content-Disposition: attachment; filename="signature.asc" Content-transfer-encoding: base64 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb2 46IEdudVBHIHYxLjIuMiAoR05V L0xpbnV4KQ0KDQppRDhEQlFBL2RoUGtJNStrUThMSmNvSVJBaV BsQUo0eGl5Y29lQTM4ZXh3M2sy N0lDMlVPcXFodlpnQ2doUWN4DQovMXl2YkE0NllJZWQ5ckZjZF R4K3M4VT0NCj1vbnI4DQotLS0t LUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCg== --0__=07BBE723DFF7BB9E8f9e8a93df938690918c07BBE723DF F7BB9E-- |
![]() |
| Thread Tools | |
| Display Modes | |
|
|