[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538658#comment-13538658 ] James Peach commented on TS-1635: - Do you have steps to reproduce? I added this URL to the TSParseUrl test suite and it parses correctly, so the bug might be somewhere other than the URL parsing ... > 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539161#comment-13539161 ] seri,Kim commented on TS-1635: -- After 3.2.0 + TS1315, this issue happend!! In Traffic Server 3.2.0, this has 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[
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
- - [%] % \"% http://%%
%\" % % \"%<{Referer}cqh>\" \"%<{User-Agent}cqh>\" %" />
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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[
https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590390#comment-13590390
]
Zhao Yongming commented on TS-1635:
---
here is 贝奇小天狼星's patch, FYI:
{code}
贝奇小天狼星 23:25:45
那个get 请求中包括域名的请求会404的。解决 了。
贝奇小天狼星 23:25:54
diff -Nur old/proxy/hdrs/URL.cc new/proxy/hdrs/URL.cc
--- old/proxy/hdrs/URL.cc 2013-02-27 14:00:24.0 +0800
+++ new/proxy/hdrs/URL.cc 2013-02-27 14:02:10.0 +0800
@@ -1066,7 +1066,9 @@
if ((end - cur >= 5) && (((cur[0] ^ 'h') | (cur[1] ^ 't') | (cur[2] ^ 't')
| (cur[3] ^ 'p') | (cur[4] ^ ':')) == 0)) {
scheme_end = cur + 4; // point to colon
url_scheme_set(heap, url, scheme_start, URL_WKSIDX_HTTP, 4,
copy_strings_p);
-} else { // some other scheme, try to parse it.
+//} else { // some other scheme, try to parse it.
+ } else if(cur[0] != '/') {
while (':' != *cur && ++cur < end)
;
if (cur < end) { // found a colon
{code}
> 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
>Assignee: Alan M. Carroll
>
> 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590391#comment-13590391 ] Zhao Yongming commented on TS-1635: --- this bug not only affect the logging, but also make remap incorrect. > 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 >Assignee: Alan M. Carroll > > 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607615#comment-13607615 ] weijin commented on TS-1635: [~evilabandon] I did a debug by using your case, and still not see the phenomenon you mentioned. Maybe the bug is in logging rather than in hdr parse. > 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 >Assignee: weijin > Fix For: 3.3.3 > > > 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608967#comment-13608967 ] Alan M. Carroll commented on TS-1635: - I understand the problem here. It is in fact a logging issue, the same one that leads to host names being lost during logging. In this case, however, it finds another URL and logs that. I'll try to work on this today. > 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 >Assignee: weijin > Fix For: 3.3.3 > > > 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608977#comment-13608977 ] evilbandon commented on TS-1635: hi Alan M. Carroll ,weijin it is not only affect the logging, but also make remap incorrect. 贝奇小天狼星's patch can fix it > 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 >Assignee: weijin > Fix For: 3.3.3 > > > 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611070#comment-13611070 ] Alan M. Carroll commented on TS-1635: - I have incorporated 贝奇小天狼星's patch and am testing that now. I see what he was trying to do and I think that is correct. > 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 >Assignee: weijin > Fix For: 3.3.3 > > Attachments: ts-1635.diff > > > 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611710#comment-13611710 ] bettydramit commented on TS-1635: - It works for me! > 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 >Assignee: weijin > Fix For: 3.3.3 > > Attachments: ts-1635.diff > > > 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
[jira] [Commented] (TS-1635) url parse BUGS IN Apache Traffic Sever 3.3.1
[ https://issues.apache.org/jira/browse/TS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613086#comment-13613086 ] Leif Hedstrom commented on TS-1635: --- Alan: Does this bug duplicate TS-1623 ? I.e. can we close one of them? > 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 >Assignee: weijin > Fix For: 3.3.3 > > Attachments: ts-1635.diff > > > 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
