Re: [squid-users] squid causing imgur problems

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Wed, 19 Sep 2012 12:27:06 +1200

On 19/09/2012 6:54 a.m., austin wonderly wrote:
> Hello, I've been having some problems with a imgur upload tool not
> working properly behind squid (hyperdesktop to be specific). this is
> what shows up in the log
> 1347932085.542 0 192.168.1.101 NONE/417 4503 POST
> http://imgur.com/api/upload - NONE/- text/html
> having said that, would you know of a way that I could fix this? if
> not, how could i make squid bypass that site completely? any help
> would really be appreciated, thanks!

417 is a message from a HTTP/1.0-only Squid to the client software that
it is using unsupported HTTP/1.1-only features (namely Expect:100-continue).
If the client *actually* supported that feature it is trying to use
there should be an immediate followup request by the client using
HTTP/1.0 compatible features and you would only see 417 log lines while
it "just worked".

The best workaround is to upgrade to Squid 3.2.1 where HTTP/1.1 support
including Expect:100-continue is exists. There are a great many client
software with various degrees of broken Expect: support.

The somewhat nasty workaround in 3.1 and 2.7 is to enable
ignore_expect_100, which will allow the request through and hope the
client wont hang for too long before deciding to send the actual POST
data when it gets no 100-continue response back from the HTTP/1.0 proxy.

Amos
Received on Wed Sep 19 2012 - 00:27:17 MDT

This archive was generated by hypermail 2.2.0 : Wed Sep 19 2012 - 12:00:04 MDT