[jira] [Closed] (TS-994) X-Forwarded-For should follow the squid way
[
https://issues.apache.org/jira/browse/TS-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao Yongming closed TS-994.
Resolution: Fixed
X-Forwarded-For should follow the squid way
---
Key: TS-994
URL: https://issues.apache.org/jira/browse/TS-994
Project: Traffic Server
Issue Type: Improvement
Components: HTTP
Affects Versions: 3.1.1
Reporter: Zhao Yongming
Assignee: Zhao Yongming
Priority: Minor
Fix For: 3.1.1
Attachments: XFF.patch
TS will append the IP in the format of:
{code}
X-Forwarded-For: 127.0.0.1, 10.32.102.41\r\n
{code}
while http://en.wikipedia.org/wiki/X-Forwarded-For says:
{code}
X-Forwarded-For: client1, proxy1, proxy2
{code}
there is 2 spaces in TS X-Forwarded-For header.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-999) Deprecate TSUrlDestroy ?
Deprecate TSUrlDestroy ? Key: TS-999 URL: https://issues.apache.org/jira/browse/TS-999 Project: Traffic Server Issue Type: Improvement Components: TS API Reporter: Leif Hedstrom Fix For: 3.1.2 This API is a complete no-op as of quite a while ago. Should we just deprecate it? Or, does anyone foresee a future where we actually need to call TSUrlDestroy? Alan? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-992) Generic portability fixes.
[ https://issues.apache.org/jira/browse/TS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-992: - Fix Version/s: 3.1.2 Generic portability fixes. -- Key: TS-992 URL: https://issues.apache.org/jira/browse/TS-992 Project: Traffic Server Issue Type: Improvement Environment: OpenBSD Reporter: Piotr Sikora Assignee: Leif Hedstrom Priority: Minor Fix For: 3.1.2 Attachments: 0001-iocore-s-swap-ts_swap-g.patch, 0001-iocore-s-swap-ts_swap-g.patch, 0002-iocore-don-t-mix-old-and-new-arpa-nameser.h-interfac.patch, 0003-mgmt-drop-getnetparms-it-isn-t-used-anywhere.patch, 0004-iocore-fix-incorrect-HostDBProcessor-getby-call.patch, 0005-tests-add-missing-link-time-flags.patch, 0006-proxy-NULL-is-defined-in-unistd.h.patch, 0007-iocore-guard-against-missing-ENOSR-and-EPROTO-defini.patch, 0008-proxy-fix-usage-of-NEED_ALTZONE_DEFINED.patch, 0009-proxy-fix-off-by-one-error-in-sscanf.patch, 0010-autoconf-improve-detection-of-available-system-heade.patch, 0011-mgmt-cast-localtime-argument-to-const-time_t.patch, 0012-examples-add-missing-sys-types.h-header.patch Bunch of patches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-992) Generic portability fixes.
[ https://issues.apache.org/jira/browse/TS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-992: Assignee: Leif Hedstrom Generic portability fixes. -- Key: TS-992 URL: https://issues.apache.org/jira/browse/TS-992 Project: Traffic Server Issue Type: Improvement Environment: OpenBSD Reporter: Piotr Sikora Assignee: Leif Hedstrom Priority: Minor Fix For: 3.1.2 Attachments: 0001-iocore-s-swap-ts_swap-g.patch, 0001-iocore-s-swap-ts_swap-g.patch, 0002-iocore-don-t-mix-old-and-new-arpa-nameser.h-interfac.patch, 0003-mgmt-drop-getnetparms-it-isn-t-used-anywhere.patch, 0004-iocore-fix-incorrect-HostDBProcessor-getby-call.patch, 0005-tests-add-missing-link-time-flags.patch, 0006-proxy-NULL-is-defined-in-unistd.h.patch, 0007-iocore-guard-against-missing-ENOSR-and-EPROTO-defini.patch, 0008-proxy-fix-usage-of-NEED_ALTZONE_DEFINED.patch, 0009-proxy-fix-off-by-one-error-in-sscanf.patch, 0010-autoconf-improve-detection-of-available-system-heade.patch, 0011-mgmt-cast-localtime-argument-to-const-time_t.patch, 0012-examples-add-missing-sys-types.h-header.patch Bunch of patches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-982) TSHttpTxnClientAddrGet provides malformed sockaddr_in
[ https://issues.apache.org/jira/browse/TS-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-982: - Fix Version/s: (was: 3.1.2) 3.1.1 Setting for 3.1.1, move to 3.1.2 if it's not urgent for the next release. TSHttpTxnClientAddrGet provides malformed sockaddr_in - Key: TS-982 URL: https://issues.apache.org/jira/browse/TS-982 Project: Traffic Server Issue Type: Bug Affects Versions: 3.0.1 Reporter: William Bardwell Assignee: Alan M. Carroll Priority: Minor Fix For: 3.1.1 It looks like PluginVCCore::set_passive_addr() and set_active_addr() never set the address family. And the address and port look like they are getting byte swapped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-993) Add OpenBSD support.
[ https://issues.apache.org/jira/browse/TS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-993: - Fix Version/s: 3.1.2 Add OpenBSD support. Key: TS-993 URL: https://issues.apache.org/jira/browse/TS-993 Project: Traffic Server Issue Type: Improvement Environment: OpenBSD Reporter: Piotr Sikora Fix For: 3.1.2 Attachments: 0001-Add-OpenBSD-support.patch Add OpenBSD support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1000) Improve Remap plugin instantiation to send the parse From and To URL
Improve Remap plugin instantiation to send the parse From and To URL -- Key: TS-1000 URL: https://issues.apache.org/jira/browse/TS-1000 Project: Traffic Server Issue Type: New Feature Components: TS API Reporter: Leif Hedstrom Assignee: Leif Hedstrom Right now, when you instantiate a remap plugin (via TSRemapNewInstance), you always get the following parameters argv[0] == The FromURL from remap.config, as a string argv[1] == The ToURL from remap.config, as a string Even though this might be useful, it would be much more useful to also have the actual parsed URL objects passed to the instantiator. In fact, the strings for the above are simply created upon plugin instantiation, e.g. err = mp-fromURL.string_get(NULL)) I'm not sure how we can accomplish this without breaking the APIs. Well, without breaking the APIs, we'd have to create a new entry point for plugins to use, e.g. TSRemapNewInstanceWithUrls() which adds the from and to URLs as arguments. I'd then argue that argv[0] and argv[1] should not be populated, i.e. make it up to the plugin implementor if he wants to call the string_get() or not. Thoughts? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-988) Upgrade ICP support for IPv6
[
https://issues.apache.org/jira/browse/TS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13133510#comment-13133510
]
Leif Hedstrom commented on TS-988:
--
Also, trying to start traffic_manager gives
[Oct 22 17:01:46.214] Manager {0x7fb82c87d800} FATAL: [LocalManager::initCCom]
Unable to find IPv4 network interface lo. Exiting...
[Oct 22 17:01:46.214] Manager {0x7fb82c87d800} FATAL: (last system error 2: No
such file or directory)
Upgrade ICP support for IPv6
Key: TS-988
URL: https://issues.apache.org/jira/browse/TS-988
Project: Traffic Server
Issue Type: Improvement
Components: Clustering
Affects Versions: 3.1.0
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll
Priority: Minor
Labels: icp, ipv6
Fix For: 3.1.2
Make ICP compatible with IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-988) Upgrade ICP support for IPv6
[
https://issues.apache.org/jira/browse/TS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13133509#comment-13133509
]
Leif Hedstrom commented on TS-988:
--
Alan: Even with ICP disabled, when I start up, I get
[Oct 22 17:00:52.259] Server {0x7f02d58be800} WARNING: ICP interface [(null)]
has no IP address
[Oct 22 17:00:52.259] Server {0x7f02d58be800} WARNING: ICP interface has no IP
address
[Oct 22 17:00:52.259] Server {0x7f02d58be800} WARNING: ICP setup, no defined
send Peer(s)
[Oct 22 17:00:52.259] Server {0x7f02d58be800} WARNING: ICP setup, no defined
send Peer(s)
Upgrade ICP support for IPv6
Key: TS-988
URL: https://issues.apache.org/jira/browse/TS-988
Project: Traffic Server
Issue Type: Improvement
Components: Clustering
Affects Versions: 3.1.0
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll
Priority: Minor
Labels: icp, ipv6
Fix For: 3.1.2
Make ICP compatible with IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (TS-988) Upgrade ICP support for IPv6
[ https://issues.apache.org/jira/browse/TS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reopened TS-988: -- Upgrade ICP support for IPv6 Key: TS-988 URL: https://issues.apache.org/jira/browse/TS-988 Project: Traffic Server Issue Type: Improvement Components: Clustering Affects Versions: 3.1.0 Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor Labels: icp, ipv6 Fix For: 3.1.2 Make ICP compatible with IPv6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
