[
https://issues.apache.org/jira/browse/TS-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs reopened TS-3140:
--------------------------------
Backport to Version: 5.2.1
Alan set up a very simple reproducing case. Fixed on master but back porting
to 5.2.x. For me the merge back was clean except for the CHANGES file.
Alan's scenario notes:
I checked out 5.2.1-rc0, did a clean build and installed fresh. I made the
following changes to records.config
proxy.config.url.remap.remap_required INT
0proxy.config.http.redirection_enabled INT
1proxy.config.http.number_of_redirections INT 3
If I start this and do "curl --proxy localhost:8080
http://docs.trafficserver.apache.org"; it crashes due to an assert.
> Traffic server crashes when there is a redirect response in cache
> -----------------------------------------------------------------
>
> Key: TS-3140
> URL: https://issues.apache.org/jira/browse/TS-3140
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 5.0.1
> Reporter: zouyu
> Assignee: Susan Hinrichs
> Labels: crash, review
> Fix For: 5.3.0
>
> Attachments: TS-3140-2.diff, TS-3140.diff
>
>
> Traffic server will crash in below steps:
> 1. Enable redirect and http cache, make sure that traffic server can cache
> redirect request & redirect response such as 302/307 response.
> 2. make a remap url in traffic server which will remap to a redirect url
> 'redirect_url_1' which points to 'www.google.com' ( note that
> 'www.google.com' is also a redirect url which may point to
> 'www.google.com.sg')
> 3. make number_of_redirections=1 in records.config.
> 4. access the 'redirect_url_1'. At first time, after access it, traffic
> server will cache the redirect response such as 307.
> 5. try to access the 'redirect_url_1' again, this time traffic server will
> crash.
> The root cause is that in above case, traffic sever will check the cache in a
> loop definitely which will exhausted the stack space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
