On Wed, Jun 10, 2009 at 11:20 PM, George
Herbert wrote:
> The 400 code makes sense. The HTTP/0.0 in the log (vs 1.0) doesn't, to me...
I think that's just a consequence of the fact that Squid never got
anything that it could parse as a valid request, so it never got as
far as negotiating a prot
On Fri, May 29, 2009 at 5:43 PM, John Horne wrote:
> I would agree with others in using 'squid -k reconfigure'. However, I
> always run 'squid -k parse' beforehand, just to make sure the config
> file is valid.
I believe "squid -k reconfigure" parses the config file and refuses
to attempt the r
On Fri, May 29, 2009 at 11:22 AM, Maxime Gaudreault
wrote:
> Is there a way to delete objects in the cache that are unused for X days
Squid manages the cache automatically. The least recently used
objects are removed as needed.
-- Ben
On Fri, May 29, 2009 at 10:44 AM, Roy M. wrote:
> I use squid as reverse proxy, however, in the backend Apache access
> log, I found that squid is using HTTP 1.0 to connect, but in the squid
> access log, it is using HTTP 1.1.
What release of Squid? Most releases don't do HTTP/1.1 at all. I
g
On Tue, May 26, 2009 at 11:18 AM, Nitin Bhadauria
wrote:
> I am using squid 3.0 with ntlm authentication. Now when a user try to
> attach a file in gmail he got an authentication windows now even if he
> enter the user name and passwd the attachment is not uploading.
I see the same thing with S
