Thanks for input. I have managed to get it functioning by using a conf file from alternate proxy. Looks like the difference is in the http_port line. To get this working it needed 'transparent'. Originally I did not put this in because the firewall was directing port 80 traffic to 3128 on the proxy box (evidently causing the issue with the broken url). We have a lot of 'frozen' desktops that are using the firewall as gateway and this can not be changed easily, so the rule was put in to send port 80 to 3128 on proxy, then allow proxy box outside access. -- Best Regards, Winfield Winfield Henry System Administrator Alamance Community College 336.506.4136 Email correspondence to and from this address may be subject to the North Carolina Public Records law and may be disclosed to third parties by an authorized state official. (NCGS.Ch. 132) >>> On 1/25/2011 at 5:16 PM, in message <b74f600fe82e928a76597f3f70f8e018@xxxxxxxxxxxxxxxxxx>, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On Tue, 25 Jan 2011 16:17:07 -0500, "Winfield Henry" wrote: >> Hi, >> I would be inclined to agree, except that the site works via two other >> squid installs that I have tried since original post. So now I think >> something else in the network is not playing nice. > > > "GET /..." are browser->origin server requests usually only existing on > port 80. If its actually arriving into squid like that its either a broken > client app, other middleware app mangling the request, or something like a > NAT redirecting port 80 native traffic through your Squid. > > I guess its wireshark time for you. > > Amos > >> >>>>> On 1/25/2011 at 4:10 PM, Amos Jeffries wrote: >> >> On Tue, 25 Jan 2011 14:52:17 -0500, "Winfield Henry" wrote: >>> Hi, >>> I have a new 2.7 squid proxy running that is giving the following error >> at >>> a login screen for a website, http://webs.com. >>> The failed url is http://members.webs.com/j_spring_security_check. >>> I will paste .conf file underneath. Any ideas on solving this would be >>> appreciated. >>> I have looked in access.log and these fetches are associated with >>> 1295985024.655 0 216.166.211.226 TCP_DENIED/400 3248 GET NONE:// - >>> NONE/- text/html >>> >>> >>> W >>> >>> >> > ---------------------------------------------------------------------------- > ---- >>> >>> Invalid Request error was encountered while trying to process the >> request: >>> >>> GET /s/login/relogin?error=1 HTTP/1.1 >> <snip> >> ... >> >>> http_port 3128 >>> >> >> This is not a browser-to-proxy request. Something is broken with that >> website. >> >> At a guess I would say they are trying to use some form of AJAX and >> screwing up the URL. >> >> Amos
