[
https://issues.apache.org/jira/browse/TS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228537#comment-15228537
]
John Rushford commented on TS-4327:
-----------------------------------
This needed a little more work to make the fixe correct. For those two cases,
call findParent() and then test to see if there is a parent and if the parent
is an origin, parent_is_proxy = false. If the parent is an origin, then
findParent() has made the correct decision with respect to the parent_result.
Otherwise, set the parent_result to PARENT_DIRECT.
The solution works correctly in the case that the request is not cacheable,
proxy.config.http.cache.cache_urls_that_look_dynamic INT 0. and the logic is
the same for CONFIG proxy.local.http.parent_proxy.disable_connect_tunneling INT
1
> Fix bug introduced with the addition of multi-site origin to parent selection.
> ------------------------------------------------------------------------------
>
> Key: TS-4327
> URL: https://issues.apache.org/jira/browse/TS-4327
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: John Rushford
> Assignee: John Rushford
> Priority: Blocker
> Fix For: 6.2.0
>
>
> Fix a bug in HttpTransact::find_server_and_update_current_info() that causes
> a segmentation fault when checking a null parent record, s->parent_result.rec
> before it has been set by findParent().
> See pull request
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
