Web Images Videos Maps News Shopping Google Mail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
(old v2.4) squid problem.
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Expand all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
Tim Woodall  
View profile   Translate to Translated (View Original)
 More options 27 Aug 2008, 23:14
Newsgroups: uk.comp.os.linux
From: Tim Woodall <devn...@woodall.me.uk>
Date: Wed, 27 Aug 2008 22:14:43 +0000 (UTC)
Local: Wed 27 Aug 2008 23:14
Subject: (old v2.4) squid problem.
I've just hit a strange problem on a system using an old version of
squid (v2.4). No idea if the problem affects newer versions of squid as
well; I've got no easy way to tell. (I don't have access to any versions
of MSIE to try)

(The system in question sits behind a firewall and is really just a
cheap access control system for outgoing traffic to the web, nothing
more, so there's no demand to upgrade the system)

The problem is a browser sending a user agent string of:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

When sent via squid the website is failing. If the browser is allowed to
connect directly then the website works (but I don't know exactly what
the browser is sending in that case)

Another computer, using the same squid but sending a user agent of
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
works fine.

Anyone seen anything similar?

The immediate solution has been to use firefox instead which also works.

tim@feynman:~$ telnet www.plumbcenter.co.uk 80
Trying 89.207.160.30...
Connected to www.plumbcenter.co.uk.
Escape character is '^]'.
GET /plumb/index.html HTTP/1.0
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

HTTP/1.1 400 Bad Request
Date: Wed, 27 Aug 2008 21:44:51 GMT
Server: Microsoft-IIS/6.0
Content-Length: 226
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br/>
</p>
</body></html>
Connection closed by foreign host.

This works if you drop the "; SV1" from the user agent. Or even replace
"; SV1" with "; SV2" or replace "5.1" with "5.0" but leave the "; SV1"
bit!

Tim.

--
God said, "div D = rho, div B = 0, curl E = - @B/@t, curl H = J + @D/@t,"
and there was light.

  http://www.woodall.me.uk/    http://www.locofungus.btinternet.co.uk/


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Dave Pickles  
View profile   Translate to Translated (View Original)
 More options 28 Aug 2008, 06:47
Newsgroups: uk.comp.os.linux
From: Dave Pickles <da...@cyw.uklinux.net>
Date: Thu, 28 Aug 2008 06:47:25 +0100
Local: Thurs 28 Aug 2008 06:47
Subject: Re: (old v2.4) squid problem.

Tim Woodall wrote:
> GET /plumb/index.html HTTP/1.0

Maybe the combination of IE sending HTTP/1.0 requests plus some kind
of 'fix' on the website for that particular browser is causing the
problem. IIRC there is a setting on IE to use HTTP/1.1 over proxies;
maybe that needs to be turned on?
--
Dave

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
C.  
View profile   Translate to Translated (View Original)
 More options 29 Aug 2008, 13:25
Newsgroups: uk.comp.os.linux
From: "C." <colin.mckin...@gmail.com>
Date: Fri, 29 Aug 2008 05:25:30 -0700 (PDT)
Local: Fri 29 Aug 2008 13:25
Subject: Re: (old v2.4) squid problem.
On 28 Aug, 06:47, Dave Pickles <da...@cyw.uklinux.net> wrote:

> Tim Woodall wrote:
> > GET /plumb/index.html HTTP/1.0

> Maybe the combination of IE sending HTTP/1.0 requests plus some kind
> of 'fix' on the website for that particular browser is causing the
> problem. IIRC there is a setting on IE to use HTTP/1.1 over proxies;
> maybe that needs to be turned on?
> --
> Dave

Certainly, if the shell example you've provided is not going through
the proxy, then the defect is at the webserver.

> tim@feynman:~$ telnet www.plumbcenter.co.uk 80
> Trying 89.207.160.30...
> Connected to www.plumbcenter.co.uk.
> Escape character is '^]'.
> GET /plumb/index.html HTTP/1.0
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

> HTTP/1.1 400 Bad Request

Note there's an obvious bug exposed already: request was HTTP/1.0 and
response is HTTP/1.1

> Server: Microsoft-IIS/6.0

hmmmmm.

IIRC Squid doesn't support re-writing of the user-agent (although
there is an unoffical patch to amend arbitary headers but for 2.5).

If you want to fix it at your end, easiest solution might be changing
the browser to use HTTP/1.1 as Dave suggests - IME this has no impact
on the performance at the browser side (it still treats everything as
HTTP/1.1) but might change the behaviour of the remote system.
Generally this is a good idea as you may be losing out on the
additional performance benefits of HTTP/1.1.

If that doesn't work, then the only other approach without changing
your squid installation (or filtering everything via awk/sed +nc)
would be to use a redirector to copy the file localy and serve it from
there. But this won't work with HTTPS.

Good luck

C.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google