[jira] [Updated] (TS-2630) Create ts/types.h used to place types shared between API and core
[ https://issues.apache.org/jira/browse/TS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang updated TS-2630: - Fix Version/s: 5.0.0 Create ts/types.h used to place types shared between API and core - Key: TS-2630 URL: https://issues.apache.org/jira/browse/TS-2630 Project: Traffic Server Issue Type: Improvement Components: Core, TS API Reporter: Yunkai Zhang Assignee: Yunkai Zhang Fix For: 5.0.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2630) Create ts/types.h used to place types shared between API and core
[ https://issues.apache.org/jira/browse/TS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang reassigned TS-2630: Assignee: Yunkai Zhang Create ts/types.h used to place types shared between API and core - Key: TS-2630 URL: https://issues.apache.org/jira/browse/TS-2630 Project: Traffic Server Issue Type: Improvement Components: Core, TS API Reporter: Yunkai Zhang Assignee: Yunkai Zhang Fix For: 5.0.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2630) Create ts/types.h used to place types shared between API and core
[ https://issues.apache.org/jira/browse/TS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang updated TS-2630: - Description: ts/types.h file is used to place common types that can be shared between internal code and TS APIs. It's hard to judge what types in ts/ts.h should be migrated to ts/types.h, so this patch is just a beginning ... Create ts/types.h used to place types shared between API and core - Key: TS-2630 URL: https://issues.apache.org/jira/browse/TS-2630 Project: Traffic Server Issue Type: Improvement Components: Core, TS API Reporter: Yunkai Zhang Assignee: Yunkai Zhang Fix For: 5.0.0 ts/types.h file is used to place common types that can be shared between internal code and TS APIs. It's hard to judge what types in ts/ts.h should be migrated to ts/types.h, so this patch is just a beginning ... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2630) Add ts/types.h to place common types shared between API and core
[ https://issues.apache.org/jira/browse/TS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang updated TS-2630: - Summary: Add ts/types.h to place common types shared between API and core (was: Create ts/types.h used to place types shared between API and core) Add ts/types.h to place common types shared between API and core Key: TS-2630 URL: https://issues.apache.org/jira/browse/TS-2630 Project: Traffic Server Issue Type: Improvement Components: Core, TS API Reporter: Yunkai Zhang Assignee: Yunkai Zhang Fix For: 5.0.0 Attachments: 0001-TS-2630-Add-ts-types.h-to-place-common-types.patch ts/types.h file is used to place common types that can be shared between internal code and TS APIs. It's hard to judge what types in ts/ts.h should be migrated to ts/types.h, so this patch is just a beginning ... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2630) Add ts/types.h to place common types shared between API and core
[
https://issues.apache.org/jira/browse/TS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931846#comment-13931846
]
James Peach commented on TS-2630:
-
This looks pretty good. I think that types that are specific to the plugin API
(e.g. {{TSPluginRegistrationInfo}}, {{TSFetchUrlParams}}) should stay in
{{ts/ts.h}}. We don't need to do that for the first commit; that's something
that we can fine-tune over time.
It would be better to put {{ts/types.h.in}} somewhere under the iocore
directory (maybe {{iocore/api/ts/types.h.in}}) to make the separation very
clear.
Add ts/types.h to place common types shared between API and core
Key: TS-2630
URL: https://issues.apache.org/jira/browse/TS-2630
Project: Traffic Server
Issue Type: Improvement
Components: Core, TS API
Reporter: Yunkai Zhang
Assignee: Yunkai Zhang
Fix For: 5.0.0
Attachments: 0001-TS-2630-Add-ts-types.h-to-place-common-types.patch
ts/types.h file is used to place common types that can be shared between
internal code and TS APIs.
It's hard to judge what types in ts/ts.h should be migrated to ts/types.h, so
this patch is just a beginning ...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Reopened] (TS-2626) Problem with Authorization: Negotiate header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee reopened TS-2626: --- James, I have confirmed that ATS-5.0.0 is removing the Referer header from request. I'll attach two tcpdumps, one before the request that goes to ATS and another with the request made from ATS to Origin. I'm attaching my configs too. Any help would be nice. Thanks in advance Problem with Authorization: Negotiate header ( Forward Mode ) - Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: ATS-3.2.2-working.txt, ATS-5.0.0-broken.txt, after-intercept-ATS-5.0.0.txt, before-intercept-ATS-5.0.0.txt, cache.config, plugin.config, records.config, storage.config We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Authorization: Negotiate header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: storage.config records.config plugin.config cache.config before-intercept-ATS-5.0.0.txt after-intercept-ATS-5.0.0.txt Problem with Authorization: Negotiate header ( Forward Mode ) - Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: ATS-3.2.2-working.txt, ATS-5.0.0-broken.txt, after-intercept-ATS-5.0.0.txt, before-intercept-ATS-5.0.0.txt, cache.config, plugin.config, records.config, storage.config We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2612) Introduce TSHttpConnectWithProtoStack() API
[
https://issues.apache.org/jira/browse/TS-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931912#comment-13931912
]
ASF subversion and git services commented on TS-2612:
-
Commit 628dad9551ed7eb9617572a8dae17465fc2a797d in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=628dad9 ]
TS-2612 Fix building out of source tree, and a few other build errors
Introduce TSHttpConnectWithProtoStack() API
---
Key: TS-2612
URL: https://issues.apache.org/jira/browse/TS-2612
Project: Traffic Server
Issue Type: New Feature
Components: TS API
Reporter: Yunkai Zhang
Assignee: Yunkai Zhang
Labels: api-addition, review
Fix For: 5.0.0
Attachments:
0004-TS-2612-Indroduce-TSHttpConnectWithProtoStack-API.patch
This ticket was split from SPDY ticket(TS-2431), and it based on extended
FetchSM ticket(TS-1062);
For some plugins that using TSHttpConnect() API to do request, the Logging
module can't know which protocol type is used, so I add a new API and
relatived tyeps:
{code}
/**
TSClientProtoStack represents what protocols are used by
the client. It may be composed by several TSProtoType.
The value of TSProtoType indicates bit-offset that can
be mapped to TSClientProtoStack by bit shifting.
For example, TLS+SPDY can be mapped to protocol stack:
proto_stack = (1u TS_PROTO_TLS) | (1u TS_PROTO_SPDY)
For the sake of brevity, TS_PROTO_TCP is usually omitted in
protocol stack.
*/
typedef enum {
/* Transport protocols (0~11) */
TS_PROTO_UDP = 0,
TS_PROTO_TCP = 1,
TS_PROTO_TLS = 2, /* TLS/SSL */
/* Application protocols (12~31) */
TS_PROTO_HTTP = 12,
TS_PROTO_SPDY = 13,
TS_PROTO_RTMP = 14,
TS_PROTO_WBSK = 15, /* WebSocket */
} TSProtoType;
typedef uint32_t TSClientProtoStack;
tsapi TSVConn TSHttpConnectWithProtoStack(struct sockaddr const* addr,
TSClientProtoStack proto_stack);
{code}
After introducing TSHttpConnectWithProtoStack() API, TSHttpConnect() API
would be a special case of it:
{code}
TSVConn
TSHttpConnect(sockaddr const* addr)
{
return TSHttpConnectWithProtoStack(addr, (1u TS_PROTO_HTTP));
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2626) Problem with Authorization: Negotiate header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931925#comment-13931925 ] Tommy Lee commented on TS-2626: --- root@ATS-Desenv:/usr/local/cache/etc/trafficserver# /usr/local/cache/bin/traffic_line -r proxy.config.http.referer_filter 0 root@ATS-Desenv:/usr/local/cache/etc/trafficserver# Problem with Authorization: Negotiate header ( Forward Mode ) - Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: ATS-3.2.2-working.txt, ATS-5.0.0-broken.txt, after-intercept-ATS-5.0.0.txt, before-intercept-ATS-5.0.0.txt, cache.config, plugin.config, records.config, storage.config We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2630) Add ts/types.h to place common types shared between API and core
[ https://issues.apache.org/jira/browse/TS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931926#comment-13931926 ] Yunkai Zhang commented on TS-2630: -- agree, I'll update it later. Add ts/types.h to place common types shared between API and core Key: TS-2630 URL: https://issues.apache.org/jira/browse/TS-2630 Project: Traffic Server Issue Type: Improvement Components: Core, TS API Reporter: Yunkai Zhang Assignee: Yunkai Zhang Fix For: 5.0.0 Attachments: 0001-TS-2630-Add-ts-types.h-to-place-common-types.patch ts/types.h file is used to place common types that can be shared between internal code and TS APIs. It's hard to judge what types in ts/ts.h should be migrated to ts/types.h, so this patch is just a beginning ... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2626) Problem with Referer Header ( Forward Mode )
[
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932058#comment-13932058
]
James Peach commented on TS-2626:
-
I expect this this is turned off, but could you also check
{{proxy.config.http.anonymize_remove_referer}}?
Problem with Referer Header ( Forward Mode )
Key: TS-2626
URL: https://issues.apache.org/jira/browse/TS-2626
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Reporter: Tommy Lee
Attachments: ATS-3.2.2-working.txt, ATS-5.0.0-broken.txt,
after-intercept-ATS-5.0.0.txt, before-intercept-ATS-5.0.0.txt, cache.config,
plugin.config, records.config, storage.config
We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some
websites that uses Authorization Header.
We always get 401 ( Unauthorized ) response.
I'm attaching two debug files. One with ATS-3.2.2 that's working and one with
ATS-5.0.0 that's broken.
Almost the same records.config for both tests.
I'm looking for changes in source code too. I'll update the issue if I find
an answer.
To devs: Could the question mark after the exchange can cause that ? This
is the only modification between these two versions.
ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange
Thanks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932061#comment-13932061 ] James Peach commented on TS-2626: - There is an anon debug tag that will log if we remove the Referrer header. Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: ATS-3.2.2-working.txt, ATS-5.0.0-broken.txt, after-intercept-ATS-5.0.0.txt, before-intercept-ATS-5.0.0.txt, cache.config, plugin.config, records.config, storage.config We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: (was: ATS-5.0.0-broken.txt) Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: (was: records.config) Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: (was: after-intercept-ATS-5.0.0.txt) Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: (was: ATS-3.2.2-working.txt) Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: (was: cache.config) Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932172#comment-13932172 ] Tommy Lee commented on TS-2626: --- James, Could you please look at tcpdump attachment ? The only difference is a ? ( question mark ) after exchange. Please note that the client requests exchange?, but the ATS removes ? of exchange while speaks to Origin. This behaviour doesn't occur with ATS-3.3.2. Do you think that behaviour could cause this problem ? Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: (was: before-intercept-ATS-5.0.0.txt) Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2626: -- Attachment: (was: storage.config) Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2626: -- Fix Version/s: 5.0.0 Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Fix For: 5.0.0 Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2626) Problem with Referer Header ( Forward Mode )
[ https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932287#comment-13932287 ] James Peach commented on TS-2626: - Interesting. This looks like the change for TS-2235. Could you revert 1ab59b435498e1c77fce9463d6072778edaa2798 and see whether that helps? Problem with Referer Header ( Forward Mode ) Key: TS-2626 URL: https://issues.apache.org/jira/browse/TS-2626 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Tommy Lee Fix For: 5.0.0 Attachments: tcpdump.txt We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some websites that uses Authorization Header. We always get 401 ( Unauthorized ) response. I'm attaching two debug files. One with ATS-3.2.2 that's working and one with ATS-5.0.0 that's broken. Almost the same records.config for both tests. I'm looking for changes in source code too. I'll update the issue if I find an answer. To devs: Could the question mark after the exchange can cause that ? This is the only modification between these two versions. ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange? ATS-5.0.0 GET - GET http://webmail.candidomendes.edu.br/exchange Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2631) Header_rewrite should support changing destination in non-remap case.
Brian Geffon created TS-2631: Summary: Header_rewrite should support changing destination in non-remap case. Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Geffon reassigned TS-2631: Assignee: Brian Geffon Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2632) Range request will always lock object in cache, even thought it's rarely cacheable
Leif Hedstrom created TS-2632: - Summary: Range request will always lock object in cache, even thought it's rarely cacheable Key: TS-2632 URL: https://issues.apache.org/jira/browse/TS-2632 Project: Traffic Server Issue Type: Bug Components: Cache, HTTP Reporter: Leif Hedstrom Right now, if a client sends a Range: request, we still lock the URL in the cache, under the assumption that it will be written to. Since we don't support partial objects, in almost all cases, we'll not write the object and therefore release the object. I suggest we change this such that we never try to write lock a URL in the presence of a Range: header in the client request. This will allow other requests to go to origin faster, and better yet, it allows a request without a Range: header to properly lock the URL for writing. This turns out to be important for implementing e.g. background filling as a plugin. There is one use case where this might be useful; If the origin does not respond with a 206 (partial object), we can now cache the full object. However, this is a pretty rare case, and for someone to support this, all you have to do is to remove the Range: header on the request. I'm opening up this bug right now for discussion, if anyone have any concerns about this change, please let me know. It is an incompatible change, without configuration options, but that should be ok for the v5.0.0 release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932487#comment-13932487 ] ASF subversion and git services commented on TS-2631: - Commit fa6224047720655882123f304d476868fba95425 in trafficserver's branch refs/heads/master from [~briang] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=fa62240 ] [TS-2631] header_rewrite to support new destinations in global plugin case Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932488#comment-13932488 ] ASF subversion and git services commented on TS-2631: - Commit cca8867973ae68ee51332eb9c19aebea0f4779d2 in trafficserver's branch refs/heads/master from [~briang] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=cca8867 ] [TS-2631] header_rewrite to support new destinations in global plugin case Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Geffon updated TS-2631: - Fix Version/s: 5.0.0 Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon Fix For: 5.0.0 header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Geffon resolved TS-2631. -- Resolution: Fixed Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932489#comment-13932489 ] ASF subversion and git services commented on TS-2631: - Commit 9f7afd8c952121a53762ad966ff207cc27d055b9 in trafficserver's branch refs/heads/master from [~briang] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=9f7afd8 ] [TS-2631] header_rewrite to support new destinations in global plugin case Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932486#comment-13932486 ] ASF subversion and git services commented on TS-2631: - Commit 50a583f7e4ef467b6c7f7af3fa6bb25ba4b0dfee in trafficserver's branch refs/heads/master from [~briang] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=50a583f ] [TS-2631] header_rewrite to support new destinations in global plugin case Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932490#comment-13932490 ] ASF subversion and git services commented on TS-2631: - Commit 5701441b6d329d652f557091fe5996df978faaa1 in trafficserver's branch refs/heads/master from [~briang] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=5701441 ] [TS-2631] Header_rewrite add SkipRemap operator Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2612) Introduce TSHttpConnectWithProtoStack() API
[
https://issues.apache.org/jira/browse/TS-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932543#comment-13932543
]
ASF subversion and git services commented on TS-2612:
-
Commit 09844ea4ad3a38346c0c88a24b3eece0920136fa in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=09844ea ]
TS-2612 Fix build problems related to %ld
Introduce TSHttpConnectWithProtoStack() API
---
Key: TS-2612
URL: https://issues.apache.org/jira/browse/TS-2612
Project: Traffic Server
Issue Type: New Feature
Components: TS API
Reporter: Yunkai Zhang
Assignee: Yunkai Zhang
Labels: api-addition, review
Fix For: 5.0.0
Attachments:
0004-TS-2612-Indroduce-TSHttpConnectWithProtoStack-API.patch
This ticket was split from SPDY ticket(TS-2431), and it based on extended
FetchSM ticket(TS-1062);
For some plugins that using TSHttpConnect() API to do request, the Logging
module can't know which protocol type is used, so I add a new API and
relatived tyeps:
{code}
/**
TSClientProtoStack represents what protocols are used by
the client. It may be composed by several TSProtoType.
The value of TSProtoType indicates bit-offset that can
be mapped to TSClientProtoStack by bit shifting.
For example, TLS+SPDY can be mapped to protocol stack:
proto_stack = (1u TS_PROTO_TLS) | (1u TS_PROTO_SPDY)
For the sake of brevity, TS_PROTO_TCP is usually omitted in
protocol stack.
*/
typedef enum {
/* Transport protocols (0~11) */
TS_PROTO_UDP = 0,
TS_PROTO_TCP = 1,
TS_PROTO_TLS = 2, /* TLS/SSL */
/* Application protocols (12~31) */
TS_PROTO_HTTP = 12,
TS_PROTO_SPDY = 13,
TS_PROTO_RTMP = 14,
TS_PROTO_WBSK = 15, /* WebSocket */
} TSProtoType;
typedef uint32_t TSClientProtoStack;
tsapi TSVConn TSHttpConnectWithProtoStack(struct sockaddr const* addr,
TSClientProtoStack proto_stack);
{code}
After introducing TSHttpConnectWithProtoStack() API, TSHttpConnect() API
would be a special case of it:
{code}
TSVConn
TSHttpConnect(sockaddr const* addr)
{
return TSHttpConnectWithProtoStack(addr, (1u TS_PROTO_HTTP));
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2598) Expose HttpDebugNames to public plugin APIs
[
https://issues.apache.org/jira/browse/TS-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932575#comment-13932575
]
Leif Hedstrom commented on TS-2598:
---
Latest proposal is:
{code}
tsapi const char* TSHttpServerStateNameLookup(TSServerState state);
tsapi const char* TSHttpHookNameLookup(TSHttpHookID hook);
tsapi const char* TSHttpEventNameLookup(TSEvent event);
{code}
Expose HttpDebugNames to public plugin APIs
---
Key: TS-2598
URL: https://issues.apache.org/jira/browse/TS-2598
Project: Traffic Server
Issue Type: New Feature
Components: TS API
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Labels: api-addition
Fix For: 5.0.0
It'd be really useful to expose all the HttpDebugNames:: functions into one
(or several?) API calls.
Either
{code}
const char* TSGetDebugName(type, ID);
{code}
where type would be a new enum of e.g.
typedef enum
{
TS_DEBUG_STATE_NAME,
TS_DEBUG_METHOD_NAME,
TS_DEBUG_EVENT_NAME,
...
} TSDebugNameID;
or perhaps
{code}
const char* TSGetDebugStateName(id);
const char* TSGetDebugMethodName(id);
...
{code}
I personally favor the former, it's more easily extended with future
additions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2631) Header_rewrite should support changing destination in non-remap case.
[ https://issues.apache.org/jira/browse/TS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932610#comment-13932610 ] ASF subversion and git services commented on TS-2631: - Commit f9b6c350186780b3271d35794a3cbec570c9f4fe in trafficserver's branch refs/heads/master from [~briang] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f9b6c35 ] Revert [TS-2631] Improve HeaderRewrite set-destination: using Condition operator instead of hard coded strings This reverts commit 0f6e5c99cc6a3d1dc2cc2131b4e8b27f0ad8b381. Header_rewrite should support changing destination in non-remap case. - Key: TS-2631 URL: https://issues.apache.org/jira/browse/TS-2631 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Brian Geffon Assignee: Brian Geffon Fix For: 5.0.0 header_rewrite currently does not support changing the destination in the non-remap plugin case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2633) 406 negative responses being cached for too long
[ https://issues.apache.org/jira/browse/TS-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2633: -- Assignee: Bryan Call 406 negative responses being cached for too long Key: TS-2633 URL: https://issues.apache.org/jira/browse/TS-2633 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 4.0.2 Reporter: David Carlin Assignee: Bryan Call Fix For: 5.0.0 Settings: proxy.config.http.negative_caching_enabled = 1 proxy.config.http.negative_caching_lifetime = 500 406 response is being cached, but lifetime isn't being adhered to. They are cached for much longer, perhaps indefinitely. I have seen Age: increase to several hours. With proxy.config.http.negative_caching_enabled = 0 then 406 responses are not cached. Bryan pointed out that the docs don't list 406 as one of the cached negative responses: http://trafficserver.readthedocs.org/en/latest/reference/configuration/records.config.en.html The value of proxy.config.http.cache.ignore_accept_mismatch has no bearing on this issue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2056) When proxy.config.http.negative_caching_enabled = 1 we cache errors even if Cache-Control: no-cache is sent from the origin
[
https://issues.apache.org/jira/browse/TS-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2056:
--
Assignee: Bryan Call
When proxy.config.http.negative_caching_enabled = 1 we cache errors even if
Cache-Control: no-cache is sent from the origin
---
Key: TS-2056
URL: https://issues.apache.org/jira/browse/TS-2056
Project: Traffic Server
Issue Type: Bug
Reporter: Phil Sorber
Assignee: Bryan Call
Labels: C
Fix For: 5.0.0
{noformat}
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain
Cache-Control: no-cache
Date: Sun, 21 Jul 2013 17:20:00 GMT
Expires: Sun, 21 Jul 2013 17:50:00 GMT
Age: 38
Content-Length: 40
Connection: keep-alive
Via: http/1.1 XX (ApacheTrafficServer/3.3.5-dev [uScHs f p eN:t cCHi
p s ])
Server: ATS/3.3.5-dev
{noformat}
While this is a grey area since we are already breaking the spec by negative
caching, I think we should still not cache this when explicitly told not to
by the origin and [~zwoop] agrees!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2633) 406 negative responses being cached for too long
[ https://issues.apache.org/jira/browse/TS-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2633: -- Fix Version/s: 5.0.0 406 negative responses being cached for too long Key: TS-2633 URL: https://issues.apache.org/jira/browse/TS-2633 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 4.0.2 Reporter: David Carlin Fix For: 5.0.0 Settings: proxy.config.http.negative_caching_enabled = 1 proxy.config.http.negative_caching_lifetime = 500 406 response is being cached, but lifetime isn't being adhered to. They are cached for much longer, perhaps indefinitely. I have seen Age: increase to several hours. With proxy.config.http.negative_caching_enabled = 0 then 406 responses are not cached. Bryan pointed out that the docs don't list 406 as one of the cached negative responses: http://trafficserver.readthedocs.org/en/latest/reference/configuration/records.config.en.html The value of proxy.config.http.cache.ignore_accept_mismatch has no bearing on this issue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-1633) add new stat sync type: TS_STAT_SYNC_MAX
[ https://issues.apache.org/jira/browse/TS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932676#comment-13932676 ] Leif Hedstrom commented on TS-1633: --- [~ushachar] Ping on this bug? add new stat sync type: TS_STAT_SYNC_MAX Key: TS-1633 URL: https://issues.apache.org/jira/browse/TS-1633 Project: Traffic Server Issue Type: Bug Components: Stats Reporter: Yakov Kopel Assignee: Uri Shachar Fix For: 5.0.0 Attachments: stat_max_ver_1.diff Adding a new stat sync type - max. This is a good type of stat to find peaks in the stats. It can be very useful with the stat clear api (after the fix - TS-1631). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-1633) add new stat sync type: TS_STAT_SYNC_MAX
[ https://issues.apache.org/jira/browse/TS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1633: -- Fix Version/s: (was: sometime) 5.0.0 add new stat sync type: TS_STAT_SYNC_MAX Key: TS-1633 URL: https://issues.apache.org/jira/browse/TS-1633 Project: Traffic Server Issue Type: Bug Components: Stats Reporter: Yakov Kopel Assignee: Uri Shachar Fix For: 5.0.0 Attachments: stat_max_ver_1.diff Adding a new stat sync type - max. This is a good type of stat to find peaks in the stats. It can be very useful with the stat clear api (after the fix - TS-1631). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2619) TSRecordDump has a bad declaration
[
https://issues.apache.org/jira/browse/TS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Sorber updated TS-2619:
Assignee: (was: Phil Sorber)
TSRecordDump has a bad declaration
--
Key: TS-2619
URL: https://issues.apache.org/jira/browse/TS-2619
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
Priority: Blocker
Fix For: 5.0.0
{{TSRecordDump}} is declared as taking a {{TSRecordType}} constant. However,
this API also is defined to be able to operate on a {{TSRecordType}} bit
mask. When you do this, you get the following compiler error:
{code}
/opt/ats/include/ts/ts.h|3083 col 14| note: candidate function not viable: no
known conversion from 'int' to 'TSRecordType' for 1st argument
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (TS-2619) TSRecordDump has a bad declaration
[
https://issues.apache.org/jira/browse/TS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Sorber reassigned TS-2619:
---
Assignee: Phil Sorber
TSRecordDump has a bad declaration
--
Key: TS-2619
URL: https://issues.apache.org/jira/browse/TS-2619
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
Assignee: Phil Sorber
Priority: Blocker
Fix For: 5.0.0
{{TSRecordDump}} is declared as taking a {{TSRecordType}} constant. However,
this API also is defined to be able to operate on a {{TSRecordType}} bit
mask. When you do this, you get the following compiler error:
{code}
/opt/ats/include/ts/ts.h|3083 col 14| note: candidate function not viable: no
known conversion from 'int' to 'TSRecordType' for 1st argument
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (TS-2634) Build broken on Ubuntu Saucy
Phil Sorber created TS-2634: --- Summary: Build broken on Ubuntu Saucy Key: TS-2634 URL: https://issues.apache.org/jira/browse/TS-2634 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber libhwloc not linked properly on ubuntu 13.10: /usr/bin/ld: ../lib/ts/.libs/libtsutil.so: undefined reference to symbol 'hwloc_get_type_depth' /usr/lib/x86_64-linux-gnu/libhwloc.so: error adding symbols: DSO missing from command line -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2634) Build broken on Ubuntu Saucy
[ https://issues.apache.org/jira/browse/TS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2634: Assignee: Leif Hedstrom Build broken on Ubuntu Saucy Key: TS-2634 URL: https://issues.apache.org/jira/browse/TS-2634 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Assignee: Leif Hedstrom libhwloc not linked properly on ubuntu 13.10: /usr/bin/ld: ../lib/ts/.libs/libtsutil.so: undefined reference to symbol 'hwloc_get_type_depth' /usr/lib/x86_64-linux-gnu/libhwloc.so: error adding symbols: DSO missing from command line -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2634) Build broken on Ubuntu Saucy
[
https://issues.apache.org/jira/browse/TS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932859#comment-13932859
]
Leif Hedstrom commented on TS-2634:
---
Looks like some linker defaults have changed (--as-needed enabled). So a couple
of options.
1. Add an explicit -lhwloc to mgmt/Makefile.am, i.e.
{code}
diff --git a/mgmt/Makefile.am b/mgmt/Makefile.am
index 55c105a..873b886 100644
--- a/mgmt/Makefile.am
+++ b/mgmt/Makefile.am
@@ -106,6 +106,7 @@ traffic_manager_LDADD = \
$(top_builddir)/proxy/shared/liberror.a \
$(top_builddir)/proxy/shared/libdiagsconfig.a \
@LIBRESOLV@ @LIBEXPAT@ @LIBPCRE@ @LIBTCL@ @LIBCAP@ \
+ @hwloc_LIBS@ \
-lm
# Must do it this way or the dependencies aren't detected.
{code}
2. Restore the old default, the equivalent of doing this (which makes the build
work too):
{code}
make CXX='c++ -Wl,--no-as-needed'
{code}
Build broken on Ubuntu Saucy
Key: TS-2634
URL: https://issues.apache.org/jira/browse/TS-2634
Project: Traffic Server
Issue Type: Bug
Reporter: Phil Sorber
Assignee: Leif Hedstrom
libhwloc not linked properly on ubuntu 13.10:
/usr/bin/ld: ../lib/ts/.libs/libtsutil.so: undefined reference to symbol
'hwloc_get_type_depth'
/usr/lib/x86_64-linux-gnu/libhwloc.so: error adding symbols: DSO missing from
command line
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2634) Build broken on Ubuntu Saucy
[
https://issues.apache.org/jira/browse/TS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932861#comment-13932861
]
James Peach commented on TS-2634:
-
{{--as-needed}} should be what we want; if it works sensibly.
Build broken on Ubuntu Saucy
Key: TS-2634
URL: https://issues.apache.org/jira/browse/TS-2634
Project: Traffic Server
Issue Type: Bug
Reporter: Phil Sorber
Assignee: Leif Hedstrom
libhwloc not linked properly on ubuntu 13.10:
/usr/bin/ld: ../lib/ts/.libs/libtsutil.so: undefined reference to symbol
'hwloc_get_type_depth'
/usr/lib/x86_64-linux-gnu/libhwloc.so: error adding symbols: DSO missing from
command line
--
This message was sent by Atlassian JIRA
(v6.2#6252)
