On 24.01.2011 21:32, Henrik Nordström wrote:
Sure. Revision 11172. Drops those method checks.
Thanks guys, you're great! Problem is solved with the latest version
from the repository.
(sorry, it took me a while to actually find time to test it...)
David
Hi list,
We're testing Squid (3.1.6) as a reverse proxy to accelerate our web
site. Now we have discovered a major issue: Squid does not accept empty
POSTs (and probably PUTs) that don't have a content-length header, and
returns HTTP/411. All works fine if we bypass the proxy.
Since this is
On 20.01.2011 14:24, Ralf Hildebrandt wrote:
* David Gublerd...@doodle.com:
Hi list,
We're testing Squid (3.1.6) as a reverse proxy to accelerate our web
site. Now we have discovered a major issue: Squid does not accept
empty POSTs (and probably PUTs) that don't have a content-length
header,
On 15.12.2010 11:14, Amos Jeffries wrote:
All the reverse proxy servers will be run by us, so I consider them
trusted. But since Amazon does not provide availability guarantees or
stable IP addresses and load may change, we might have to add or remove
instances on the fly. I'd like to have a
Hi Amos, thanks for your response!
Be careful, very very careful. ESPN is the example of the month for doing
this badly. Their site refuses to open for anyone browsing from a host with
local proxy installed.
Thanks for the warning. I'll try it with a proxy server before putting
this into
I'm experimenting with Squid 3.0 as a reverse proxy. Currently, there
are two Squids running on the same machine, one for HTTP and one for
HTTPS (Squid must use HTTPS for the connection to our web server if and
only if the user did use HTTPS to contact Squid. I couldn't find another
way to do
