[jira] [Commented] (TS-462) Support TLS Server Name Indication (SNI) negotiation
[ https://issues.apache.org/jira/browse/TS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219954#comment-13219954 ] Igor Galić commented on TS-462: --- I would suggest to primarily treat SAN as orthogonal feature we need to implement into the SSL stack anyway -- like verifying backends we connect to via SSL - those could have SAN certs. Let's not have those almost independent features impede each other. > Support TLS Server Name Indication (SNI) negotiation > > > Key: TS-462 > URL: https://issues.apache.org/jira/browse/TS-462 > Project: Traffic Server > Issue Type: New Feature > Components: SSL >Affects Versions: 3.0.0 >Reporter: Leif Hedstrom >Assignee: Igor Galić >Priority: Minor > Labels: ssl > Fix For: 3.1.5 > > > We should support TLS Server Name Indication (SNI). This would allow for well > behaved TLS clients to negotiate the certificate, without requiring a new IP > for every site / certificate used. -- 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-462) Support TLS Server Name Indication (SNI) negotiation
[ https://issues.apache.org/jira/browse/TS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220069#comment-13220069 ] Leif Hedstrom commented on TS-462: -- Igor, not sure I understand, but my point is, if there's no way to configure the "domain" in ssl_multicert.config, we might have issues with certain types of certificates. Sure, we can punt on it for now, but at some point, it'd have to be dealt with, no? > Support TLS Server Name Indication (SNI) negotiation > > > Key: TS-462 > URL: https://issues.apache.org/jira/browse/TS-462 > Project: Traffic Server > Issue Type: New Feature > Components: SSL >Affects Versions: 3.0.0 >Reporter: Leif Hedstrom >Assignee: Igor Galić >Priority: Minor > Labels: ssl > Fix For: 3.1.5 > > > We should support TLS Server Name Indication (SNI). This would allow for well > behaved TLS clients to negotiate the certificate, without requiring a new IP > for every site / certificate used. -- 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-462) Support TLS Server Name Indication (SNI) negotiation
[ https://issues.apache.org/jira/browse/TS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220086#comment-13220086 ] James Peach commented on TS-462: What's SAN? > Support TLS Server Name Indication (SNI) negotiation > > > Key: TS-462 > URL: https://issues.apache.org/jira/browse/TS-462 > Project: Traffic Server > Issue Type: New Feature > Components: SSL >Affects Versions: 3.0.0 >Reporter: Leif Hedstrom >Assignee: Igor Galić >Priority: Minor > Labels: ssl > Fix For: 3.1.5 > > > We should support TLS Server Name Indication (SNI). This would allow for well > behaved TLS clients to negotiate the certificate, without requiring a new IP > for every site / certificate used. -- 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-462) Support TLS Server Name Indication (SNI) negotiation
[ https://issues.apache.org/jira/browse/TS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220100#comment-13220100 ] Leif Hedstrom commented on TS-462: -- Subject Alternatative Name or some such. Basically, you can have > 1 domain in a cert, other than the mandatory domain. E.g. X509v3 Subject Alternative Name: DNS:*.foo.com, DNS:*.bar.com, DNS:*.fie.org I don't think it's always been in the specs, but I've used this for a long time for my private certs. If I recall (I'm probably wrong), you used to have to put multiple names in the CN. Also, http://tools.ietf.org/html/rfc6125 tries to clarify all those I think. > Support TLS Server Name Indication (SNI) negotiation > > > Key: TS-462 > URL: https://issues.apache.org/jira/browse/TS-462 > Project: Traffic Server > Issue Type: New Feature > Components: SSL >Affects Versions: 3.0.0 >Reporter: Leif Hedstrom >Assignee: Igor Galić >Priority: Minor > Labels: ssl > Fix For: 3.1.5 > > > We should support TLS Server Name Indication (SNI). This would allow for well > behaved TLS clients to negotiate the certificate, without requiring a new IP > for every site / certificate used. -- 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-968) During/after daily logfile roll, trafficserver seg faults (Sig 11)
[
https://issues.apache.org/jira/browse/TS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220136#comment-13220136
]
Zhao Yongming commented on TS-968:
--
is this issue still valid for now? can you test if it still valid with current
stable release and the current git master tree?
> During/after daily logfile roll, trafficserver seg faults (Sig 11)
> --
>
> Key: TS-968
> URL: https://issues.apache.org/jira/browse/TS-968
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.0.1
> Environment: Ubuntu 10.10, 2.6.35-24-virtual
>Reporter: Drew Rothstein
> Fix For: 3.1.4
>
>
> Every day at 00:00:00 after/during the log file roll, I see a segfault. Here
> are the past couple days:
> [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile
> /usr/local/var/log/trafficserver/error.log was rolled to
> /usr/local/var/log/trafficserver/error.log_trafficserver02.20110921.00h00m06s-20110922.00h00m00s.old.
> [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile
> /usr/local/var/log/trafficserver/squid.log was rolled to
> /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
> [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile
> /usr/local/var/log/trafficserver/extended2.log was rolled to
> /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /usr/local/bin/traffic_server - STACK TRACE:
> [Sep 22 00:00:17.729] Manager {140722071643936} FATAL:
> [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
> [Sep 22 00:00:17.729] Manager {140722071643936} FATAL: (last system error
> 104: Connection reset by peer)
> [Sep 22 00:00:17.730] Manager {140722071643936} NOTE:
> [LocalManager::mgmtShutdown] Executing shutdown request.
> [Sep 22 00:00:17.730] Manager {140722071643936} NOTE:
> [LocalManager::processShutdown] Executing process shutdown request.
> [Sep 22 00:00:17.730] Manager {140722071643936} ERROR:
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep 22 00:00:17.730] Manager {140722071643936} ERROR: (last system error
> 32: Broken pipe)
> [E. Mgmt] log ==> [TrafficManager] using root directory '/usr/local'
> [Sep 22 00:00:17.786] {140131209512736} STATUS: opened
> /usr/local/var/log/trafficserver/manager.log
> [Sep 22 00:00:17.786] {140131209512736} NOTE: updated diags config
> [Sep 22 00:00:17.805] Manager {140131209512736} NOTE:
> [ClusterCom::ClusterCom] Node running on OS: 'Linux' Release:
> '2.6.35-24-virtual'
> [Sep 22 00:00:17.805] Manager {140131209512736} NOTE:
> [LocalManager::listenForProxy] Listening on port: 80
> [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: [TrafficManager] Setup
> complete
> [Sep 22 00:00:18.827] Manager {140131209512736} NOTE:
> [LocalManager::startProxy] Launching ts process
> [TrafficServer] using root directory '/usr/local'
> [Sep 22 00:00:18.849] Manager {140131209512736} NOTE:
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep 22 00:00:18.849] Manager {140131209512736} NOTE: [Alarms::signalAlarm]
> Server Process born
> [Sep 22 00:00:19.874] {47510015031936} STATUS: opened
> /usr/local/var/log/trafficserver/diags.log
> [Sep 22 00:00:19.874] {47510015031936} NOTE: updated diags config
> [Sep 22 00:00:19.879] Server {47510015031936} NOTE: cache clustering disabled
> [Sep 22 00:00:19.908] Server {47510015031936} NOTE: cache clustering disabled
> [Sep 22 00:00:20.019] Server {47510015031936} NOTE: logging initialized[7],
> logging_mode = 3
> [Sep 22 00:00:20.032] Server {47510015031936} NOTE: traffic server running
> [Sep 22 00:00:20.045] Server {47510028859136} NOTE: cache enabled
> [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile
> /usr/local/var/log/trafficserver/error.log was rolled to
> /usr/local/var/log/trafficserver/error.log_trafficserver02.20110922.00h00m11s-20110923.00h00m00s.old.
> [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile
> /usr/local/var/log/trafficserver/squid.log was rolled to
> /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
> [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile
> /usr/local/var/log/trafficserver/extended2.log was rolled to
> /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /usr/local/bin/traffic_server - STACK TRACE:
> [Sep 23 00:00:14.668] Manager {140131209512736} FATAL:
> [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
> [Sep 23 0
[jira] [Commented] (TS-1051) Updating logs_xml.config requires full restart
[
https://issues.apache.org/jira/browse/TS-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220145#comment-13220145
]
Zhao Yongming commented on TS-1051:
---
I don't think that will happen in current master tree and stable releases.
please check the result of:
traffic_line -r proxy.config.log.custom_logs_enabled
it must be set to 1 to enable logs_xml.config
> Updating logs_xml.config requires full restart
> --
>
> Key: TS-1051
> URL: https://issues.apache.org/jira/browse/TS-1051
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.1.2
>Reporter: Billy Vierra
>Assignee: Leif Hedstrom
> Fix For: 3.1.4
>
>
> Using SVN Rev: 1214051
> URL: http://svn.apache.org/repos/asf/trafficserver/traffic/trunk
> upon adding a new LogObject and doing traffic_line -x you get the following
> in traffic.out
> [Dec 14 12:31:48.533] Manager {0x7f2f2abef700} NOTE: User has changed config
> file logs_xml.config
> However it does not go into effect (new log is not created). Upon full
> restart: trafficserver stop, trafficserver start it will add the new log file
> as expected.
> Not sure if it is a bug with docs or in code.
--
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-968) During/after daily logfile roll, trafficserver seg faults (Sig 11)
[
https://issues.apache.org/jira/browse/TS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao Yongming reassigned TS-968:
Assignee: Zhao Yongming
> During/after daily logfile roll, trafficserver seg faults (Sig 11)
> --
>
> Key: TS-968
> URL: https://issues.apache.org/jira/browse/TS-968
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.0.1
> Environment: Ubuntu 10.10, 2.6.35-24-virtual
>Reporter: Drew Rothstein
>Assignee: Zhao Yongming
> Fix For: 3.1.4
>
>
> Every day at 00:00:00 after/during the log file roll, I see a segfault. Here
> are the past couple days:
> [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile
> /usr/local/var/log/trafficserver/error.log was rolled to
> /usr/local/var/log/trafficserver/error.log_trafficserver02.20110921.00h00m06s-20110922.00h00m00s.old.
> [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile
> /usr/local/var/log/trafficserver/squid.log was rolled to
> /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
> [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile
> /usr/local/var/log/trafficserver/extended2.log was rolled to
> /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /usr/local/bin/traffic_server - STACK TRACE:
> [Sep 22 00:00:17.729] Manager {140722071643936} FATAL:
> [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
> [Sep 22 00:00:17.729] Manager {140722071643936} FATAL: (last system error
> 104: Connection reset by peer)
> [Sep 22 00:00:17.730] Manager {140722071643936} NOTE:
> [LocalManager::mgmtShutdown] Executing shutdown request.
> [Sep 22 00:00:17.730] Manager {140722071643936} NOTE:
> [LocalManager::processShutdown] Executing process shutdown request.
> [Sep 22 00:00:17.730] Manager {140722071643936} ERROR:
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep 22 00:00:17.730] Manager {140722071643936} ERROR: (last system error
> 32: Broken pipe)
> [E. Mgmt] log ==> [TrafficManager] using root directory '/usr/local'
> [Sep 22 00:00:17.786] {140131209512736} STATUS: opened
> /usr/local/var/log/trafficserver/manager.log
> [Sep 22 00:00:17.786] {140131209512736} NOTE: updated diags config
> [Sep 22 00:00:17.805] Manager {140131209512736} NOTE:
> [ClusterCom::ClusterCom] Node running on OS: 'Linux' Release:
> '2.6.35-24-virtual'
> [Sep 22 00:00:17.805] Manager {140131209512736} NOTE:
> [LocalManager::listenForProxy] Listening on port: 80
> [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: [TrafficManager] Setup
> complete
> [Sep 22 00:00:18.827] Manager {140131209512736} NOTE:
> [LocalManager::startProxy] Launching ts process
> [TrafficServer] using root directory '/usr/local'
> [Sep 22 00:00:18.849] Manager {140131209512736} NOTE:
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep 22 00:00:18.849] Manager {140131209512736} NOTE: [Alarms::signalAlarm]
> Server Process born
> [Sep 22 00:00:19.874] {47510015031936} STATUS: opened
> /usr/local/var/log/trafficserver/diags.log
> [Sep 22 00:00:19.874] {47510015031936} NOTE: updated diags config
> [Sep 22 00:00:19.879] Server {47510015031936} NOTE: cache clustering disabled
> [Sep 22 00:00:19.908] Server {47510015031936} NOTE: cache clustering disabled
> [Sep 22 00:00:20.019] Server {47510015031936} NOTE: logging initialized[7],
> logging_mode = 3
> [Sep 22 00:00:20.032] Server {47510015031936} NOTE: traffic server running
> [Sep 22 00:00:20.045] Server {47510028859136} NOTE: cache enabled
> [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile
> /usr/local/var/log/trafficserver/error.log was rolled to
> /usr/local/var/log/trafficserver/error.log_trafficserver02.20110922.00h00m11s-20110923.00h00m00s.old.
> [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile
> /usr/local/var/log/trafficserver/squid.log was rolled to
> /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
> [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile
> /usr/local/var/log/trafficserver/extended2.log was rolled to
> /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /usr/local/bin/traffic_server - STACK TRACE:
> [Sep 23 00:00:14.668] Manager {140131209512736} FATAL:
> [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
> [Sep 23 00:00:14.668] Manager {140131209512736} FATAL: (last system error
> 104: Connection reset by peer)
> [Sep 23 00:00:14.668] Ma
[jira] [Assigned] (TS-1051) Updating logs_xml.config requires full restart
[
https://issues.apache.org/jira/browse/TS-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao Yongming reassigned TS-1051:
-
Assignee: Zhao Yongming (was: Leif Hedstrom)
> Updating logs_xml.config requires full restart
> --
>
> Key: TS-1051
> URL: https://issues.apache.org/jira/browse/TS-1051
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.1.2
>Reporter: Billy Vierra
>Assignee: Zhao Yongming
> Fix For: 3.1.4
>
>
> Using SVN Rev: 1214051
> URL: http://svn.apache.org/repos/asf/trafficserver/traffic/trunk
> upon adding a new LogObject and doing traffic_line -x you get the following
> in traffic.out
> [Dec 14 12:31:48.533] Manager {0x7f2f2abef700} NOTE: User has changed config
> file logs_xml.config
> However it does not go into effect (new log is not created). Upon full
> restart: trafficserver stop, trafficserver start it will add the new log file
> as expected.
> Not sure if it is a bug with docs or in code.
--
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-1124) Move a few plugins into main repo.
Move a few plugins into main repo. -- Key: TS-1124 URL: https://issues.apache.org/jira/browse/TS-1124 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 Moving regex_remap, header_filter and stats_over_http into main git repo (in plugins). I've tried to preserve history, but it gets a little wonky due to the change in directory structure. But the history is there :). -- 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-1002) log unmapped HOST when pristine_host_hdr disabled
[
https://issues.apache.org/jira/browse/TS-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao Yongming reassigned TS-1002:
-
Assignee: Zhao Yongming
> log unmapped HOST when pristine_host_hdr disabled
> -
>
> Key: TS-1002
> URL: https://issues.apache.org/jira/browse/TS-1002
> Project: Traffic Server
> Issue Type: Wish
> Components: Logging
>Reporter: Conan Wang
>Assignee: Zhao Yongming
>Priority: Minor
> Fix For: 3.1.5
>
>
> I want to log user request's "Host" in http header before remap. I write
> logs_xml.config, like: %<{Host}cqh>
> When proxy.config.url_remap.pristine_host_hdr is enabled, I will get the
> right "Host" which is not rewritten.
> When disable the config, I always get the rewritten/mapped "Host" which is
> not what I need.
> logs_xml reference:
> http://trafficserver.apache.org/docs/v2/admin/logfmts.htm#66912
--
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-1002) log unmapped HOST when pristine_host_hdr disabled
[
https://issues.apache.org/jira/browse/TS-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220150#comment-13220150
]
Zhao Yongming commented on TS-1002:
---
I think this is fixed in the git master?
{code}
zymtest1 trafficserver # tail -n 100 taobaomiss.log
00:40:39 127.0.0.1 fe80::746d:74ff:febf:ebaa 428 200 TCP_MISS
"http://cdn.zymlinux.net/trafficserver/0"; 411 402 0 text/plain
http://zymlinux.net/trafficserver/0 "-"
00:40:39 127.0.0.1 fe80::746d:74ff:febf:ebaa 475 200 TCP_MISS
"http://cdn.zymlinux.net/trafficserver/ts75.png"; 418 404 9520 image/png
http://zymlinux.net/trafficserver/ts75.png "-"
00:42:42 127.0.0.1 fe80::746d:74ff:febf:ebaa 54 200 TCP_REFRESH_HIT
"http://cdn.zymlinux.net/trafficserver/ts75.png"; 418 404 9520 image/png
http://zymlinux.net/trafficserver/ts75.png "-"
00:42:42 127.0.0.1 fe80::746d:74ff:febf:ebaa 53 200 TCP_MISS
"http://cdn.zymlinux.net/trafficserver/0"; 411 402 0 text/plain
http://zymlinux.net/trafficserver/0 "-"
zymtest1 trafficserver # traffic_line -r
proxy.config.url_remap.pristine_host_hdr
0
zymtest1 trafficserver # grep cdn.zymlinux.net /etc/trafficserver/remap.config
map http://cdn.zymlinux.net/http://zymlinux.net
zymtest1 trafficserver #
{code}
> log unmapped HOST when pristine_host_hdr disabled
> -
>
> Key: TS-1002
> URL: https://issues.apache.org/jira/browse/TS-1002
> Project: Traffic Server
> Issue Type: Wish
> Components: Logging
>Reporter: Conan Wang
>Priority: Minor
> Fix For: 3.1.5
>
>
> I want to log user request's "Host" in http header before remap. I write
> logs_xml.config, like: %<{Host}cqh>
> When proxy.config.url_remap.pristine_host_hdr is enabled, I will get the
> right "Host" which is not rewritten.
> When disable the config, I always get the rewritten/mapped "Host" which is
> not what I need.
> logs_xml reference:
> http://trafficserver.apache.org/docs/v2/admin/logfmts.htm#66912
--
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-462) Support TLS Server Name Indication (SNI) negotiation
[ https://issues.apache.org/jira/browse/TS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220164#comment-13220164 ] James Peach commented on TS-462: I think I'd rather deal with this in a separate JIRA. Maybe Igor would be so good as to file one describing the requirements? > Support TLS Server Name Indication (SNI) negotiation > > > Key: TS-462 > URL: https://issues.apache.org/jira/browse/TS-462 > Project: Traffic Server > Issue Type: New Feature > Components: SSL >Affects Versions: 3.0.0 >Reporter: Leif Hedstrom >Assignee: Igor Galić >Priority: Minor > Labels: ssl > Fix For: 3.1.5 > > > We should support TLS Server Name Indication (SNI). This would allow for well > behaved TLS clients to negotiate the certificate, without requiring a new IP > for every site / certificate used. -- 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-1125) POST's with Expect: 100-continue are slowed by delayed 100 response.
POST's with Expect: 100-continue are slowed by delayed 100 response. Key: TS-1125 URL: https://issues.apache.org/jira/browse/TS-1125 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.2 Environment: TS 3.0.2 going to Apache 2.2 web server Reporter: William Bardwell Priority: Minor Sending a post like: POST / HTTP/1.1 Host: www.example.com Content-Length: 10 Expect: 100-continue directly to the web server immediately sends back: HTTP/1.1 100 Continue And then when the post data is sent, a status 200 response comes back. But when going through ATS the "HTTP/1.1 100 Continue" is not sent immediately, and instead is sent after the POST data has been received. This is legal, but it makes clients that are hoping for a 100 continue to wait a little while hoping to get that, ATS should forward that response through immediately. Note: I see curl using "Expect: 100-continue" with > 1024 bytes of post data, but web searching indicates that some Microsoft products also use it. -- 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] [Resolved] (TS-1124) Move a few plugins into main repo.
[ https://issues.apache.org/jira/browse/TS-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-1124. --- Resolution: Fixed > Move a few plugins into main repo. > -- > > Key: TS-1124 > URL: https://issues.apache.org/jira/browse/TS-1124 > Project: Traffic Server > Issue Type: New Feature > Components: Plugins >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 3.1.3 > > > Moving regex_remap, header_filter and stats_over_http into main git repo (in > plugins). I've tried to preserve history, but it gets a little wonky due to > the change in directory structure. But the history is there :). -- 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-1124) Move a few plugins into main repo.
[ https://issues.apache.org/jira/browse/TS-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220438#comment-13220438 ] Leif Hedstrom commented on TS-1124: --- Commits include: eee2913090d40fed0d0398fe872b95c95d6b3c23 1f38e9e3a0b298f2c72a570fd1232c9adb2992d5 a5044fcc5266018cd1ba2d9700ebfc429c148921 8cfc3b71a0c557b50464945768e7d832723bebe1 fdebccc1d58a7c8ec30e54302963bfe4cdd89340 a6a83eef0ba3adaf88e42b0613d6774ea1232a75 199219146227957b5d8101440c32c755c2a2e727 0c89201b4dc3cb2686420565e41adfc3ee04d762 901ff98a5860d133f2a7db383bc1d074dad3a950 > Move a few plugins into main repo. > -- > > Key: TS-1124 > URL: https://issues.apache.org/jira/browse/TS-1124 > Project: Traffic Server > Issue Type: New Feature > Components: Plugins >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 3.1.3 > > > Moving regex_remap, header_filter and stats_over_http into main git repo (in > plugins). I've tried to preserve history, but it gets a little wonky due to > the change in directory structure. But the history is there :). -- 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-1126) traffic_server is unable to bind 127.0.0.1:8084 (the default mgmt port) on OSX
traffic_server is unable to bind 127.0.0.1:8084 (the default mgmt port) on OSX
--
Key: TS-1126
URL: https://issues.apache.org/jira/browse/TS-1126
Project: Traffic Server
Issue Type: Bug
Components: Management API
Affects Versions: 3.1.2
Reporter: Leif Hedstrom
Priority: Critical
Fix For: 3.1.3
When we start up, it errors out binding 8084:
[Mar 1 16:40:33.937] Server {0x7fff74cdb960} ERROR: Could not bind or listen
to port 8084 (error: -1)
[Mar 1 16:40:33.937] Server {0x7fff74cdb960} WARNING: unable to listen on port
8084: -1 49, Can't assign requested address
--
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-1002) log unmapped HOST when pristine_host_hdr disabled
[
https://issues.apache.org/jira/browse/TS-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220704#comment-13220704
]
Conan Wang commented on TS-1002:
not fix in my test.
CONFIG proxy.config.url_remap.pristine_host_hdr INT 0
maphttp://cdn.zymlinux.nethttp://zymlinux.net
squid.log
1330668375.573 119 127.0.0.1 TCP_MISS/200 9821 GET
http://zymlinux.net/trafficserver/ts75.png - DIRECT/zymlinux.net image/png -
custom.log ( first field is %<{Host}cqh> )
zymlinux.net - 0 TCP_MISS [02/Mar/2012:14:06:15 +0800] "GET
/trafficserver/ts75.png HTTP/1.1" 200 9520 "-" "-" "curl/7.21.4
(universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8r zlib/1.2.5"
> log unmapped HOST when pristine_host_hdr disabled
> -
>
> Key: TS-1002
> URL: https://issues.apache.org/jira/browse/TS-1002
> Project: Traffic Server
> Issue Type: Wish
> Components: Logging
>Reporter: Conan Wang
>Assignee: Zhao Yongming
>Priority: Minor
> Fix For: 3.1.5
>
>
> I want to log user request's "Host" in http header before remap. I write
> logs_xml.config, like: %<{Host}cqh>
> When proxy.config.url_remap.pristine_host_hdr is enabled, I will get the
> right "Host" which is not rewritten.
> When disable the config, I always get the rewritten/mapped "Host" which is
> not what I need.
> logs_xml reference:
> http://trafficserver.apache.org/docs/v2/admin/logfmts.htm#66912
--
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
