[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] [Created] (TS-1636) Crash after using up a lot of RAM
Aron Xu created TS-1636: --- Summary: Crash after using up a lot of RAM Key: TS-1636 URL: https://issues.apache.org/jira/browse/TS-1636 Project: Traffic Server Issue Type: Bug Reporter: Aron Xu We are running traffic server in forward proxy mode, on an 8 core Xeon with 16GiB RAM, and 500GiB disk allocated in storage.config. The operating system is Debian wheezy amd64, TS version is the git snapshot of the last commit of 2012-12-08, which is available in Debian experimental. The cache runs quite good since the last restart at 18th December, and it uses more and more memory over the time, which is the expected behavior. But I find in log that the process crashed today and restarted automatically, and the only thing I know is that the process had used over 8GiB RAM, but no accurate number. Log entry: NOTE: Traffic Server received Sig 11: Segmentation fault /usr/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x2b7f99340030] /usr/bin/traffic_server(RangeTransform::transform_to_range()+0x80)[0x4e5c90] /usr/bin/traffic_server(RangeTransform::handle_event(int, void*)+0x308)[0x4e7a98] /usr/bin/traffic_server(EThread::process_event(Event*, int)+0x92)[0x66a062] /usr/bin/traffic_server(EThread::execute()+0x5db)[0x66aa6b] /usr/bin/traffic_server[0x669202] /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x2b7f99337b50] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b7f9b7e9a7d] -- 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-1625) ATS doesn't support localhost services for full IPT connections
[ https://issues.apache.org/jira/browse/TS-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537794#comment-13537794 ] Aidan McGurn commented on TS-1625: -- new (INTD)patch is final fix - this exposes an INK API which allows the user should they want to rewrite the header (dest) to also change the backend connection to a proxy - this is more general than the fist attached patch and allows all cases not just localhost > ATS doesn't support localhost services for full IPT connections > --- > > Key: TS-1625 > URL: https://issues.apache.org/jira/browse/TS-1625 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Aidan McGurn > Attachments: CCOD-309-IPT_LocalServices.patch, > INTD-1782-IPT_LocalServices.patch > > > We have at least 2 use cases where we want to connect the backend (OS) > connection to localhost. > This currently won't work under full IPT as the backend connection socket is > bound to the client src ip. It needs to be bound to localhost also otherwise > e.g. ---> 127.0.0.1 //this will fail > needs to be: 127.0.0.1 > 127.0.0.1 (for ipv6: ::1 ---> ::1) -- 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] [Updated] (TS-1625) ATS doesn't support localhost services for full IPT connections
[ https://issues.apache.org/jira/browse/TS-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan McGurn updated TS-1625: - Attachment: INTD-1782-IPT_LocalServices.patch > ATS doesn't support localhost services for full IPT connections > --- > > Key: TS-1625 > URL: https://issues.apache.org/jira/browse/TS-1625 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Aidan McGurn > Attachments: CCOD-309-IPT_LocalServices.patch, > INTD-1782-IPT_LocalServices.patch > > > We have at least 2 use cases where we want to connect the backend (OS) > connection to localhost. > This currently won't work under full IPT as the backend connection socket is > bound to the client src ip. It needs to be bound to localhost also otherwise > e.g. ---> 127.0.0.1 //this will fail > needs to be: 127.0.0.1 > 127.0.0.1 (for ipv6: ::1 ---> ::1) -- 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
