[jira] [Resolved] (TS-1909) remove duplicate listen socket conditioning
[ https://issues.apache.org/jira/browse/TS-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-1909. - Resolution: Fixed > remove duplicate listen socket conditioning > --- > > Key: TS-1909 > URL: https://issues.apache.org/jira/browse/TS-1909 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: James Peach >Assignee: James Peach >Priority: Minor > Fix For: 3.3.3 > > > Listen sockets get conditioned in Server::setup_fd_for_listen() and > Server::listen(). These code paths are largely duplicated for no reason. -- 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-1909) remove duplicate listen socket conditioning
[ https://issues.apache.org/jira/browse/TS-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661273#comment-13661273 ] ASF subversion and git services commented on TS-1909: - Commit fe5d32cd82683be1354b9f2854ec85944e260e3c in branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=fe5d32c ] TS-1909: remove duplicate listen socket conditioning Socket options were applied to the listen sockets in both Server::setup_fd_for_listen() and Server::listen(). There's really only a need for one of these, so remove all the duplicated code. > remove duplicate listen socket conditioning > --- > > Key: TS-1909 > URL: https://issues.apache.org/jira/browse/TS-1909 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: James Peach >Assignee: James Peach >Priority: Minor > Fix For: 3.3.3 > > > Listen sockets get conditioned in Server::setup_fd_for_listen() and > Server::listen(). These code paths are largely duplicated for no reason. -- 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-1909) remove duplicate listen socket conditioning
[ https://issues.apache.org/jira/browse/TS-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661265#comment-13661265 ] ASF subversion and git services commented on TS-1909: - Commit 0522abd5655bd8ae62f5c80e590083a8c728e0c7 in branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0522abd ] Revert "TS-1909: remove duplicate listen socket conditioning" This reverts commit 03cbafef3ce88c4fe39f866532f212a4da820afa. This seems to be causing failures in the following regression tests: SDK_API_HttpAltInfo, SDK_API_HttpTxnTransform, SDK_API_HttpTxnCache, SDK_API_HttpSsn and SDK_API_HttpHookAdd. > remove duplicate listen socket conditioning > --- > > Key: TS-1909 > URL: https://issues.apache.org/jira/browse/TS-1909 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: James Peach >Assignee: James Peach >Priority: Minor > Fix For: 3.3.3 > > > Listen sockets get conditioned in Server::setup_fd_for_listen() and > Server::listen(). These code paths are largely duplicated for no reason. -- 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-1909) remove duplicate listen socket conditioning
[ https://issues.apache.org/jira/browse/TS-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661257#comment-13661257 ] ASF subversion and git services commented on TS-1909: - Commit 03cbafef3ce88c4fe39f866532f212a4da820afa in branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=03cbafe ] TS-1909: remove duplicate listen socket conditioning Socket options were applied to the listen sockets in both Server::setup_fd_for_listen() and Server::listen(). There's really only a need for one of these, so remove all the duplicated code. > remove duplicate listen socket conditioning > --- > > Key: TS-1909 > URL: https://issues.apache.org/jira/browse/TS-1909 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: James Peach >Assignee: James Peach >Priority: Minor > Fix For: 3.3.3 > > > Listen sockets get conditioned in Server::setup_fd_for_listen() and > Server::listen(). These code paths are largely duplicated for no reason. -- 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-1910) Backport to make 3.2.x compile with Clang
[
https://issues.apache.org/jira/browse/TS-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1910:
--
Attachment: TS-1910.diff
This is what I've got so far, I'm adding this to the STATUS file to vote on.
> Backport to make 3.2.x compile with Clang
> -
>
> Key: TS-1910
> URL: https://issues.apache.org/jira/browse/TS-1910
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
>Reporter: Leif Hedstrom
> Fix For: 3.2.5
>
> Attachments: TS-1910.diff
>
>
> There are too many bugs to clone for this, so I'm combining it all into one.
> The commits to backport, so far, are:
> {code}
> b216afa3
> 58205af1
> dc3f8ffa
> 81f9f418
> {code}
--
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-1910) Backport to make 3.2.x compile with Clang
[
https://issues.apache.org/jira/browse/TS-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1910:
--
Fix Version/s: 3.2.5
> Backport to make 3.2.x compile with Clang
> -
>
> Key: TS-1910
> URL: https://issues.apache.org/jira/browse/TS-1910
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
>Reporter: Leif Hedstrom
> Fix For: 3.2.5
>
>
> There are too many bugs to clone for this, so I'm combining it all into one.
> The commits to backport, so far, are:
> {code}
> b216afa3
> 58205af1
> dc3f8ffa
> 81f9f418
> {code}
--
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-1910) Backport to make 3.2.x compile with Clang
Leif Hedstrom created TS-1910:
-
Summary: Backport to make 3.2.x compile with Clang
Key: TS-1910
URL: https://issues.apache.org/jira/browse/TS-1910
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
There are too many bugs to clone for this, so I'm combining it all into one.
The commits to backport, so far, are:
{code}
b216afa3
58205af1
dc3f8ffa
81f9f418
{code}
--
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-1909) remove duplicate listen socket conditioning
James Peach created TS-1909: --- Summary: remove duplicate listen socket conditioning Key: TS-1909 URL: https://issues.apache.org/jira/browse/TS-1909 Project: Traffic Server Issue Type: Bug Components: Core Reporter: James Peach Listen sockets get conditioned in Server::setup_fd_for_listen() and Server::listen(). These code paths are largely duplicated for no reason. -- 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-1909) remove duplicate listen socket conditioning
[ https://issues.apache.org/jira/browse/TS-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach updated TS-1909: Priority: Minor (was: Major) Fix Version/s: 3.3.3 Assignee: James Peach > remove duplicate listen socket conditioning > --- > > Key: TS-1909 > URL: https://issues.apache.org/jira/browse/TS-1909 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: James Peach >Assignee: James Peach >Priority: Minor > Fix For: 3.3.3 > > > Listen sockets get conditioned in Server::setup_fd_for_listen() and > Server::listen(). These code paths are largely duplicated for no reason. -- 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-1896) Cleanup duplication of TS_HAS_ and HAVE_ symbols
[ https://issues.apache.org/jira/browse/TS-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661007#comment-13661007 ] ASF subversion and git services commented on TS-1896: - Commit cf01c1d27a21805b69811a76db49e171911613b7 in branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=cf01c1d ] Added TS-1896. > Cleanup duplication of TS_HAS_ and HAVE_ symbols > - > > Key: TS-1896 > URL: https://issues.apache.org/jira/browse/TS-1896 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 3.3.3 > > > There's a pretty significant duplication of symbols in ink_config.h.in and > ink_autoconf.h.in, and I don't see a reason for this (other than confusion). -- 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-1896) Cleanup duplication of TS_HAS_ and HAVE_ symbols
[ https://issues.apache.org/jira/browse/TS-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661008#comment-13661008 ] ASF subversion and git services commented on TS-1896: - Commit 9be0f6be66f8254140c0d2ce061b7a7b9388a0a6 in branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=9be0f6b ] TS-1896 Cleanup of unused defines, sometimes duplicated > Cleanup duplication of TS_HAS_ and HAVE_ symbols > - > > Key: TS-1896 > URL: https://issues.apache.org/jira/browse/TS-1896 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 3.3.3 > > > There's a pretty significant duplication of symbols in ink_config.h.in and > ink_autoconf.h.in, and I don't see a reason for this (other than confusion). -- 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-1908) ATS shouldn't accept connections to a down destination in transparent mode
Ebrahim Mohammadi created TS-1908: - Summary: ATS shouldn't accept connections to a down destination in transparent mode Key: TS-1908 URL: https://issues.apache.org/jira/browse/TS-1908 Project: Traffic Server Issue Type: New Feature Reporter: Ebrahim Mohammadi ATS shouldn't accept connections whose destination host/port is down while working in transparent mode. Currently hosts in a network with a transparent ATS intercepting all to-port-80 TCP connection will see TCP port 80 of all IP addresses as open and accepting connections, while most of them are in fact closed. This is against "transparency" of the transparent web cache. -- 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-1831) traffic_logstats should not always require log dir access
[
https://issues.apache.org/jira/browse/TS-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach updated TS-1831:
Fix Version/s: 3.5.0
Yeh 3.5.0 is fine. I'm not getting to this any time soon.
> traffic_logstats should not always require log dir access
> -
>
> Key: TS-1831
> URL: https://issues.apache.org/jira/browse/TS-1831
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
>Reporter: James Peach
> Fix For: 3.5.0
>
>
> When running "make check", the traffic_logstats test fails if the host system
> does not have a current Traffic Server installation:
> {code}
> FAIL: tests/test_logstats_json
> ==
> unable to change to log directory
> "/home/vagrant/build/proxy/var/log/trafficserver" [2 'No such file or
> directory']
> please set correct path in env variable TS_ROOT
> {code}
> It's unreasonable for traffic_logstats to absolutely require the logdir to be
> present. We should investigate whether the chdir failure can be weakened to a
> warning instead of a hard error.
--
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] [Assigned] (TS-1882) ATS doesn't warn about unknown config items
[ https://issues.apache.org/jira/browse/TS-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-1882: - Assignee: Leif Hedstrom > ATS doesn't warn about unknown config items > --- > > Key: TS-1882 > URL: https://issues.apache.org/jira/browse/TS-1882 > Project: Traffic Server > Issue Type: Bug > Components: Configuration >Reporter: Ebrahim Mohammadi >Assignee: Leif Hedstrom > Fix For: 3.3.3 > > > Apache Traffic Server doesn't warn about unknown configuration file items. It > can cause huge confusions, specially in case of trying to get features of a > newer version to work on an older installed version by mistake, as I found > out the hard way! -- 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-1831) traffic_logstats should not always require log dir access
[
https://issues.apache.org/jira/browse/TS-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660892#comment-13660892
]
Leif Hedstrom commented on TS-1831:
---
Seeing that things works now, do we still need to fix this? Move it out to
v3.5.0 for now?
> traffic_logstats should not always require log dir access
> -
>
> Key: TS-1831
> URL: https://issues.apache.org/jira/browse/TS-1831
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
>Reporter: James Peach
>
> When running "make check", the traffic_logstats test fails if the host system
> does not have a current Traffic Server installation:
> {code}
> FAIL: tests/test_logstats_json
> ==
> unable to change to log directory
> "/home/vagrant/build/proxy/var/log/trafficserver" [2 'No such file or
> directory']
> please set correct path in env variable TS_ROOT
> {code}
> It's unreasonable for traffic_logstats to absolutely require the logdir to be
> present. We should investigate whether the chdir failure can be weakened to a
> warning instead of a hard error.
--
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-1882) ATS doesn't warn about unknown config items
[ https://issues.apache.org/jira/browse/TS-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1882: -- Fix Version/s: 3.3.3 > ATS doesn't warn about unknown config items > --- > > Key: TS-1882 > URL: https://issues.apache.org/jira/browse/TS-1882 > Project: Traffic Server > Issue Type: Bug > Components: Configuration >Reporter: Ebrahim Mohammadi > Fix For: 3.3.3 > > > Apache Traffic Server doesn't warn about unknown configuration file items. It > can cause huge confusions, specially in case of trying to get features of a > newer version to work on an older installed version by mistake, as I found > out the hard way! -- 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-1907) Order of ipv6 and ssl options in proxy.config.http.server_ports matters
[ https://issues.apache.org/jira/browse/TS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1907: -- Fix Version/s: 3.3.3 > Order of ipv6 and ssl options in proxy.config.http.server_ports matters > --- > > Key: TS-1907 > URL: https://issues.apache.org/jira/browse/TS-1907 > Project: Traffic Server > Issue Type: Bug > Components: Configuration >Reporter: David Carlin >Assignee: Alan M. Carroll >Priority: Minor > Fix For: 3.3.3 > > > In proxy.config.http.server_ports "443:ssl:ipv6" fails but "443:ipv6:ssl" > works -- 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-1878) link libraries as needed on linux
[
https://issues.apache.org/jira/browse/TS-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1878:
--
Fix Version/s: 3.3.3
> link libraries as needed on linux
> -
>
> Key: TS-1878
> URL: https://issues.apache.org/jira/browse/TS-1878
> Project: Traffic Server
> Issue Type: Improvement
> Components: Build
>Reporter: James Peach
>Priority: Minor
> Fix For: 3.3.3
>
>
> We should pass {{-Wl,-as-needed}} to the linker on Linux to get it to strip
> unused libraries. The equivalent Darwin option is {{-Wl,-dead_strip_dylibs}}.
> See also:
> http://www.gentoo.org/proj/en/qa/asneeded.xml
>
> http://sigquit.wordpress.com/2011/02/16/why-asneeded-doesnt-work-as-expected-for-your-libraries-on-your-autotools-project/
--
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] [Assigned] (TS-1878) link libraries as needed on linux
[
https://issues.apache.org/jira/browse/TS-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-1878:
-
Assignee: James Peach
> link libraries as needed on linux
> -
>
> Key: TS-1878
> URL: https://issues.apache.org/jira/browse/TS-1878
> Project: Traffic Server
> Issue Type: Improvement
> Components: Build
>Reporter: James Peach
>Assignee: James Peach
>Priority: Minor
> Fix For: 3.3.3
>
>
> We should pass {{-Wl,-as-needed}} to the linker on Linux to get it to strip
> unused libraries. The equivalent Darwin option is {{-Wl,-dead_strip_dylibs}}.
> See also:
> http://www.gentoo.org/proj/en/qa/asneeded.xml
>
> http://sigquit.wordpress.com/2011/02/16/why-asneeded-doesnt-work-as-expected-for-your-libraries-on-your-autotools-project/
--
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-1883) SSL origin connections do not support connection timeouts
[
https://issues.apache.org/jira/browse/TS-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1883:
--
Fix Version/s: 3.3.3
> SSL origin connections do not support connection timeouts
> -
>
> Key: TS-1883
> URL: https://issues.apache.org/jira/browse/TS-1883
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, SSL
>Reporter: James Peach
> Fix For: 3.3.3
>
>
> In {{proxy/http/HttpSM.cc}}, we can see that origin connections do not
> support timeouts if the scheme is HTTPS:
> {code}
> void
> HttpSM::do_http_server_open(bool raw)
> {
> ...
> if (t_state.scheme == URL_WKSIDX_HTTPS) {
> DebugSM("http", "calling sslNetProcessor.connect_re");
> connect_action_handle = sslNetProcessor.connect_re(this,// state
> machine
>
> &t_state.current.server->addr.sa,// addr + port
>&opt);
> } else {
> ...
> // Setup the timeouts
> // Set the inactivity timeout to the connect timeout so that we
> // we fail this server if it doesn't start sending the response
> // header
> MgmtInt connect_timeout;
> if (t_state.method == HTTP_WKSIDX_POST || t_state.method ==
> HTTP_WKSIDX_PUT) {
> connect_timeout = t_state.txn_conf->post_connect_attempts_timeout;
> } else if (t_state.current.server == &t_state.parent_info) {
> connect_timeout = t_state.http_config_param->parent_connect_timeout;
> } else {
> if (t_state.pCongestionEntry != NULL)
> connect_timeout = t_state.pCongestionEntry->connect_timeout();
> else
> connect_timeout = t_state.txn_conf->connect_attempts_timeout;
> }
> DebugSM("http", "calling netProcessor.connect_s");
> connect_action_handle = netProcessor.connect_s(this, // state
> machine
>
> &t_state.current.server->addr.sa,// addr + port
> connect_timeout, &opt);
> ...
> }
> {code}
--
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-1907) Order of ipv6 and ssl options in proxy.config.http.server_ports matters
[ https://issues.apache.org/jira/browse/TS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Carlin updated TS-1907: - Priority: Minor (was: Major) > Order of ipv6 and ssl options in proxy.config.http.server_ports matters > --- > > Key: TS-1907 > URL: https://issues.apache.org/jira/browse/TS-1907 > Project: Traffic Server > Issue Type: Bug > Components: Configuration >Reporter: David Carlin >Priority: Minor > > In proxy.config.http.server_ports "443:ssl:ipv6" fails but "443:ipv6:ssl" > works -- 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] [Assigned] (TS-1907) Order of ipv6 and ssl options in proxy.config.http.server_ports matters
[ https://issues.apache.org/jira/browse/TS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll reassigned TS-1907: --- Assignee: Alan M. Carroll > Order of ipv6 and ssl options in proxy.config.http.server_ports matters > --- > > Key: TS-1907 > URL: https://issues.apache.org/jira/browse/TS-1907 > Project: Traffic Server > Issue Type: Bug > Components: Configuration >Reporter: David Carlin >Assignee: Alan M. Carroll >Priority: Minor > > In proxy.config.http.server_ports "443:ssl:ipv6" fails but "443:ipv6:ssl" > works -- 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-1907) Order of ipv6 and ssl options in proxy.config.http.server_ports matters
David Carlin created TS-1907: Summary: Order of ipv6 and ssl options in proxy.config.http.server_ports matters Key: TS-1907 URL: https://issues.apache.org/jira/browse/TS-1907 Project: Traffic Server Issue Type: Bug Components: Configuration Reporter: David Carlin In proxy.config.http.server_ports "443:ssl:ipv6" fails but "443:ipv6:ssl" works -- 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-374) Potentially eliminate lock contention on HostDB
[ https://issues.apache.org/jira/browse/TS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660778#comment-13660778 ] ASF subversion and git services commented on TS-374: Commit a85c1fa9ae8be16acd853c33df085cadc2a1a8b5 in branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=a85c1fa ] Added TS-374. > Potentially eliminate lock contention on HostDB > --- > > Key: TS-374 > URL: https://issues.apache.org/jira/browse/TS-374 > Project: Traffic Server > Issue Type: Improvement > Components: Core >Reporter: Leif Hedstrom >Assignee: Bryan Call > Fix For: 3.3.3 > > > When using as a reverse proxy, when a single (or very few) HostDB entries are > under "pressure", the try-lock there could cause us to reschedule. John > suggests we look at this as a first step towards reducing latencies under > high load, by avoiding holding the lock over multiple callbacks. -- 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-1904) gcc 4.8 complains about uninitialized struct tm
[ https://issues.apache.org/jira/browse/TS-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660755#comment-13660755 ] ASF subversion and git services commented on TS-1904: - Commit 36b34ee8c06863f9904b4253155880d793e07ae8 in branch refs/heads/3.2.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=36b34ee ] Add TS-1904 > gcc 4.8 complains about uninitialized struct tm > --- > > Key: TS-1904 > URL: https://issues.apache.org/jira/browse/TS-1904 > Project: Traffic Server > Issue Type: Bug > Components: Build >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 3.3.2 > > > And most of this code is dead anyways, so kill it by Igor's fire? -- 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-1787) gcc 4.8 complains about uninitialized struct tm
[ https://issues.apache.org/jira/browse/TS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660735#comment-13660735 ] ASF subversion and git services commented on TS-1787: - Commit 729a56bc9bfcffb9c24995a9873bada943a9a2a3 in branch refs/heads/3.2.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=729a56b ] TS-1787 gcc 4.8 complains about uninitialized struct tm > gcc 4.8 complains about uninitialized struct tm > --- > > Key: TS-1787 > URL: https://issues.apache.org/jira/browse/TS-1787 > Project: Traffic Server > Issue Type: Bug > Components: Build >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 3.3.2 > > > And most of this code is dead anyways, so kill it by Igor's fire? -- 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
