Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm a fan of the Squid proxy server and have been using it at work for our a while .. on a windows 2008 server.

It cannot handle HTTP 1.1. Does anyone know if this is fixed/available for a windows release, yet?

Is it coming? Has the Squid development stalled / died off ??

share|improve this question
We've been looking at replacing an old pix with a squid/pfsense box at a remote office -- I'd be curious to hear what the implications of the lack of HTTP 1.l support are -- does it refuse requests in 1.1 or pass them on in 1.0, and what issues does it create? – nedm Jun 29 '09 at 3:44
From our experience at our office, certain websites refuse to accept the request connection if it's not at least http1.1. I know this example is VERY trivial, but SETI is an example of this (and yes, seti has a manual setting to request in http 1.0). That said, nearly all places are a-ok, thought. – Pure.Krome Jun 30 '09 at 1:58
up vote 0 down vote accepted

There's a project to add support. Since it has no progress since the end of 2006, either it's abandoned or merged in. I'm assuming the former and recommend you try to build with it patched in.

share|improve this answer

In a limited sense, it's available.

See their roadmaps at and

For some reason, I see it on the Squid 2 roadmap, but not on squid3.

share|improve this answer
the current release for squid is 2.7, for windows. so it's on the roadmap doesn't necessarily mean its in that build, right? – Pure.Krome May 5 '09 at 5:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.