adrian at creative
Oct 9, 2009, 12:12 PM
Post #4 of 4
(342 views)
Permalink
|
It is a HTTP/1.0 vs HTTP/1.1 thing (Chunked encoding for HTTP/1.1
doesn't require you to calculate and send a Content-Length.)
Adrian
On Fri, Oct 09, 2009, Jared Mauch wrote:
> I've been having the same issue when going through my Linux+Squid+WCCP
> setup, but if the browser is configured to go direct to the proxy it
> does not seem to have the same issue. (At least so far).
>
> - Jared
>
> On Oct 9, 2009, at 2:48 PM, Adrian Chadd wrote:
>
> >A few people have asked what the specific problem is.
> >
> >http://www.squid-cache.org/mail-archive/squid-dev/200910/0089.html
> >
> >
> >
> >
> >Adrian
> >
> >On Sat, Oct 10, 2009, Adrian Chadd wrote:
> >>howdy,
> >>
> >>I'm chasing a technical contact at Facebook. There's some broken
> >>HTTP being
> >>served which is confusing Squid in a way that isn't easily, cleanly
> >>worked around.
> >>
> >>Please feel free to contact me off-list.
--
- Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support -
- $24/pm+GST entry-level VPSes w/ capped bandwidth charges available in WA -
|
