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

evilbandon commented on TS-1635:
--------------------------------

it can be reproduce easy
here is my major config content
remap.config
map http://a.b.com/ http://222.73.6.32:8080
map http://b.c.com/ http://222.73.6.32:8080
logs_xml.config
<LogFormat>
    <Format = "%<chi> - - [%<cqtn>] %<ttms> \"%<cqhm> http://%<cquuh>%<cquup> 
%<csshv>\" %<pssc> %<psql> \"%<{Referer}cqh>\" \"%<{User-Agent}cqh>\" %<crc>" />
    <Name = "httpd_combined"/>
</LogFormat>
<LogObject>
    <Format = "httpd_combined"/>
    <Filename = "stc.access.log"/>
    <RollingIntervalSec = "86400"/>
</LogObject>

I use curl command to request the ats
curl -o /dev/null 'http://a.b.com/xx.jpg?newpath=http://b.c.com'

in the ats's access log it record this request as "222.73.6.32 - - 
[24/Dec/2012:13:23:36 +0800] 0 "GET http://b.c.com/ HTTP/0.0" 200 287 "-" 
"curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 
libidn/0.6.5" TCP_MISS" 

and in the source server's access log it record this request as "222.73.6.32    
 -    -     [24/Dec/2012:13:23:36 +0800]    "GET http://b.c.com/";   
"curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 
libidn/0.6.5"       "-""

so I thought it may haapend in the url parse 

and in ats 3.2.0 stable this issue not happened
                
> url parse BUGS IN Apache Traffic Sever 3.3.1 
> ---------------------------------------------
>
>                 Key: TS-1635
>                 URL: https://issues.apache.org/jira/browse/TS-1635
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: evilbandon
>
> url parse BUGS IN Apache Traffic Sever 3.3.1 
> the request URL is http://a.b.com/xx.jpg?newpath=http://b.c.com
> but the Apache Traffic Sever 3.3.1 parse this url as http://b.c.com

--
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