[
https://issues.apache.org/jira/browse/TS-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959010#comment-13959010
]
James Peach commented on TS-2678:
---------------------------------
The craigslist response sends a 302 with no content-length and no chunking.
{code}
peach$ curl -v -o /dev/null -s http://www.craigslist.com/
* Hostname was NOT found in DNS cache
* Trying 208.82.236.145...
* Connected to www.craigslist.com (208.82.236.145) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.36.0
> Host: www.craigslist.com
> Accept: */*
>
< HTTP/1.1 302 Found
< Location: http://www.craigslist.org/
* no chunk, no close, no size. Assume close to signal end
<
{ [data not shown]
* Closing connection 0
{code}
> Some sites (e.g. craigslist) fails to load with patch in e6b9cb533bba28
> -----------------------------------------------------------------------
>
> Key: TS-2678
> URL: https://issues.apache.org/jira/browse/TS-2678
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Assignee: James Peach
> Priority: Critical
> Fix For: 5.0.0
>
>
> The commit e6b9cb533bba28, from
> TS-2559: Disconnect clients on unrecoverable origin errors
> is causing some sites to break badly:
> {code}
> curl: (52) Empty reply from server
> {code}
> or sometimes
> {code}
> HTTP/1.1 302 Found
> Location: http://www.craigslist.org/
> Date: Mon, 31 Mar 2014 02:36:51 GMT
> Age: 0
> Transfer-Encoding: chunked
> Proxy-Connection: keep-alive
> Server: ATS/5.0.0
> curl: (18) transfer closed with outstanding read data remaining
> {code}
> The first one happens most frequently in my test, and the second one is close
> to what is expected (but not quite). Both makes the page not load properly
> from any browser.
> To reproduce this, using a "default" installation, with remap.require
> disabled (so, forward proxy), I run
> {code}
> curl -D - -x localhost:8080 http://www.craigslist.com
> {code}
> I don't know what it is that Craigslist does to trigger this, but backing out
> the patch from TS-2559 does fix the problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
