Closed GoogleCodeExporter closed 9 years ago
ops workaround wont work either. Its really random. now you see soon you won't
Original comment by chudy.fernandez
on 30 Sep 2009 at 12:00
Maybe facebook having issues on their cluster? They have problems quite often
this
days... also they have very strange DDoS protection system, that block requests
with
too long headers (i had to cut off Via: and X-Forwarded-For headers!)
Original comment by nuclear...@gmail.com
on 30 Sep 2009 at 2:14
Not only facebook but contents that has Transfer-Encoding: chunked header
and some with Content-Encoding: gzip header
http://sugg.search.yahoo.net/sg/?output=fxjsonp&nresults=10&command=RNA%20from%2
0yeas
http://images.friendster.com/200909A-019/css/app_styles_profile.css
Original comment by chudy.fernandez
on 30 Sep 2009 at 5:32
client req http1.1 -> squid req http1.0 -> facebook
facebook rep http1.1 -> squid rep http1.0 -> client
server_http11 solve the problem
Original comment by chudy.fernandez
on 1 Oct 2009 at 4:09
Hm, I don't have that particular problem here. I'd love to see the full request
and reply headers there.
How long are your Via/XFF headers exactly? :)
Original comment by adrian.c...@gmail.com
on 2 Oct 2009 at 3:53
Are you seeing it now? I've been told by facebook devs that they've found and
fixed
bugs in their code.
Original comment by adrian.c...@gmail.com
on 15 Oct 2009 at 10:20
Nice. I've removed the http11 and so far its fine.
Original comment by chudy.fernandez
on 17 Oct 2009 at 6:36
Original comment by adrian.c...@gmail.com
on 18 Oct 2009 at 3:21
Original issue reported on code.google.com by
chudy.fernandez
on 30 Sep 2009 at 10:53