[ 
https://issues.apache.org/jira/browse/TS-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606873#comment-13606873
 ] 

Leif Hedstrom edited comment on TS-1106 at 3/19/13 9:45 PM:
------------------------------------------------------------

Debugged a little more on this. It looks like it fails the remap phase, calls 
HttpTransact::build_error_response(), then somehow figures out it's a 
"redirect" map, and calls it again, but this time with the redirect information.

The first call ends up being:
{code}
#3  HttpTransact::build_error_response (s=s@entry=0x7fffed9e42f8, 
status_code=status_code@entry=HTTP_STATUS_NOT_FOUND,
reason_phrase_or_null=<optimized out>, error_body_type=0x6b6a52 
"urlrouting#no_mapping",
format=0x6b9920 "Your requested URL was not found.") at 
../../../../proxy/http/HttpTransact.cc:8103
{code}

whereas the second time it is:
{code}
#3  HttpTransact::build_error_response (s=s@entry=0x7fffed9e42f8, 
status_code=status_code@entry=HTTP_STATUS_MOVED_PERMANENTLY,
reason_phrase_or_null=reason_phrase_or_null@entry=0x6cbec6 "Redirect", 
error_body_type=error_body_type@entry=0x6b69d3
"redirect#moved_permanently", format=format@entry=0x6b69b8 "%s <a 
href=\"%s\">%s</a>. %s") at ../../../../proxy/http/HttpTransact.cc:8103
{code}


I asked Bryan Call to verity with the older Yahoo version, and it looks to 
behave the same. The end result is correct (we do the right redirect), but it 
seems odd to call the build_error_response twice?
                
      was (Author: zwoop):
    Debugged a little more on this. It looks like it fails the remap phase, 
calls HttpTransact::build_error_response(), then somehow figures out it's a 
"redirect" map, and calls it again, but this time with the redirect information.

The first call ends up being:
{code}
#3  HttpTransact::build_error_response (s=s@entry=0x7fffed9e42f8, 
status_code=status_code@entry=HTTP_STATUS_NOT_FOUND, 
reason_phrase_or_null=<optimized out>, error_body_type=0x6b6a52 
"urlrouting#no_mapping", format=0x6b9920 "Your requested URL was not found.") 
at ../../../../proxy/http/HttpTransact.cc:8103
{code}

whereas the second time it is:
{
#3  HttpTransact::build_error_response (s=s@entry=0x7fffed9e42f8, 
status_code=status_code@entry=HTTP_STATUS_MOVED_PERMANENTLY, 
reason_phrase_or_null=reason_phrase_or_null@entry=0x6cbec6 "Redirect", 
error_body_type=error_body_type@entry=0x6b69d3 "redirect#moved_permanently", 
format=format@entry=0x6b69b8 "%s <a href=\"%s\">%s</a>. %s") at 
../../../../proxy/http/HttpTransact.cc:8103
}


I asked Bryan Call to verity with the older Yahoo version, and it looks to 
behave the same. The end result is correct (we do the right redirect), but it 
seems odd to call the build_error_response twice?
                  
> redirect map generates multiple Via: header entries.
> ----------------------------------------------------
>
>                 Key: TS-1106
>                 URL: https://issues.apache.org/jira/browse/TS-1106
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>    Affects Versions: 3.1.2
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 3.3.3
>
>
> It seems using the redirect rule in remap.config, ends up duplicating the 
> entry in the Via: header, e.g.
> {code}
> Via: http/1.1 kramer.ogre.com (ApacheTrafficServer/3.1.3-unstable [u c s f p 
> eS:tNc  i p s ]), http/1.1 kramer.ogre.com 
> (ApacheTrafficServer/3.1.3-unstable [u c s f p eS:tNc  i p s ])
> {code}
> I'm not sure why this happens, if it's duplicating it, or if it's going 
> through the SM twice. I know i'm not proxying twice through the box.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to