[jira] [Commented] (TS-2555) Move existing lua plugin to plugins/deprecated and rename ts_lua to lua
[ https://issues.apache.org/jira/browse/TS-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008287#comment-14008287 ] ASF subversion and git services commented on TS-2555: - Commit 14c484b414ea3be02bc5aebee650cb626fc6cc58 in trafficserver's branch refs/heads/master from [~kichan] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=14c484b ] TS-2555: more features for ts_lua - support function to add global hook, use TSError, support TSSkipRemappingSet Move existing lua plugin to plugins/deprecated and rename ts_lua to lua --- Key: TS-2555 URL: https://issues.apache.org/jira/browse/TS-2555 Project: Traffic Server Issue Type: Task Components: Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 As suggested by Igor Galic in TS-2335, to avoid namespace pollution, we could move move the old Lua plugin to plugins/deprecated, and name this one lua again from the start. From what I gather, the consensus on the mailing list was to replace the old plugin with this one. Given that the old plugin was experimental, and we've decided that all bets regarding compatibility and stability are off in experimental, I'm fairly certain we can just do that. I'd move it, for easy reference into plugins/deprecated, remove it from the build, and once the new plugin has absorbed all of its features, remove it all together. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2555) Move existing lua plugin to plugins/deprecated and rename ts_lua to lua
[ https://issues.apache.org/jira/browse/TS-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008292#comment-14008292 ] Kit Chan commented on TS-2555: -- Based on feedbacks, the last commit contains the following fixes 1) We can use ts.hook to add global hook instead of using global functions 2) We do not always add TXN_CLOSE_HOOK handler to release resources unless needed 3) We add support for TSSkipRemappingSet 4) We use TSError 5) Documentation is updated. Move existing lua plugin to plugins/deprecated and rename ts_lua to lua --- Key: TS-2555 URL: https://issues.apache.org/jira/browse/TS-2555 Project: Traffic Server Issue Type: Task Components: Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 As suggested by Igor Galic in TS-2335, to avoid namespace pollution, we could move move the old Lua plugin to plugins/deprecated, and name this one lua again from the start. From what I gather, the consensus on the mailing list was to replace the old plugin with this one. Given that the old plugin was experimental, and we've decided that all bets regarding compatibility and stability are off in experimental, I'm fairly certain we can just do that. I'd move it, for easy reference into plugins/deprecated, remove it from the build, and once the new plugin has absorbed all of its features, remove it all together. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2555) Move existing lua plugin to plugins/deprecated and rename ts_lua to lua
[ https://issues.apache.org/jira/browse/TS-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008295#comment-14008295 ] ASF subversion and git services commented on TS-2555: - Commit 9a3e5de5f2009921436069b3393a133e0c23d5d1 in trafficserver's branch refs/heads/master from [~kichan] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=9a3e5de ] TS-2555: update README.md and remove old lua plugin Move existing lua plugin to plugins/deprecated and rename ts_lua to lua --- Key: TS-2555 URL: https://issues.apache.org/jira/browse/TS-2555 Project: Traffic Server Issue Type: Task Components: Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 As suggested by Igor Galic in TS-2335, to avoid namespace pollution, we could move move the old Lua plugin to plugins/deprecated, and name this one lua again from the start. From what I gather, the consensus on the mailing list was to replace the old plugin with this one. Given that the old plugin was experimental, and we've decided that all bets regarding compatibility and stability are off in experimental, I'm fairly certain we can just do that. I'd move it, for easy reference into plugins/deprecated, remove it from the build, and once the new plugin has absorbed all of its features, remove it all together. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (TS-2555) Move existing lua plugin to plugins/deprecated and rename ts_lua to lua
[ https://issues.apache.org/jira/browse/TS-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan resolved TS-2555. -- Resolution: Fixed Move existing lua plugin to plugins/deprecated and rename ts_lua to lua --- Key: TS-2555 URL: https://issues.apache.org/jira/browse/TS-2555 Project: Traffic Server Issue Type: Task Components: Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 As suggested by Igor Galic in TS-2335, to avoid namespace pollution, we could move move the old Lua plugin to plugins/deprecated, and name this one lua again from the start. From what I gather, the consensus on the mailing list was to replace the old plugin with this one. Given that the old plugin was experimental, and we've decided that all bets regarding compatibility and stability are off in experimental, I'm fairly certain we can just do that. I'd move it, for easy reference into plugins/deprecated, remove it from the build, and once the new plugin has absorbed all of its features, remove it all together. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2844) Documentation Update for ESI plugin
[ https://issues.apache.org/jira/browse/TS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan reassigned TS-2844: Assignee: Kit Chan Documentation Update for ESI plugin --- Key: TS-2844 URL: https://issues.apache.org/jira/browse/TS-2844 Project: Traffic Server Issue Type: Task Components: Documentation, Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 Need to update the documentation for ESI Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2844) Documentation Update for ESI plugin
[ https://issues.apache.org/jira/browse/TS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-2844: - Fix Version/s: 5.0.0 Documentation Update for ESI plugin --- Key: TS-2844 URL: https://issues.apache.org/jira/browse/TS-2844 Project: Traffic Server Issue Type: Task Components: Documentation, Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 Need to update the documentation for ESI Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2844) Documentation Update for ESI plugin
Kit Chan created TS-2844: Summary: Documentation Update for ESI plugin Key: TS-2844 URL: https://issues.apache.org/jira/browse/TS-2844 Project: Traffic Server Issue Type: Task Components: Documentation, Plugins Reporter: Kit Chan Need to update the documentation for ESI Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2844) Documentation Update for ESI plugin
[ https://issues.apache.org/jira/browse/TS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008296#comment-14008296 ] ASF subversion and git services commented on TS-2844: - Commit 84517e5129156ea3325d9337fa2e9158f13dab13 in trafficserver's branch refs/heads/master from [~kichan] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=84517e5 ] TS-2844: update documentation for ESI plugin Documentation Update for ESI plugin --- Key: TS-2844 URL: https://issues.apache.org/jira/browse/TS-2844 Project: Traffic Server Issue Type: Task Components: Documentation, Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 Need to update the documentation for ESI Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work started] (TS-2844) Documentation Update for ESI plugin
[ https://issues.apache.org/jira/browse/TS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TS-2844 started by Kit Chan. Documentation Update for ESI plugin --- Key: TS-2844 URL: https://issues.apache.org/jira/browse/TS-2844 Project: Traffic Server Issue Type: Task Components: Documentation, Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 Need to update the documentation for ESI Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2555) Move existing lua plugin to plugins/deprecated and rename ts_lua to lua
[ https://issues.apache.org/jira/browse/TS-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008298#comment-14008298 ] ASF subversion and git services commented on TS-2555: - Commit b304cf0c16a7f8e47d10e499874c283fa3ba420b in trafficserver's branch refs/heads/master from [~kichan] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=b304cf0 ] TS-2555: update README.md for ts_lua plugin Move existing lua plugin to plugins/deprecated and rename ts_lua to lua --- Key: TS-2555 URL: https://issues.apache.org/jira/browse/TS-2555 Project: Traffic Server Issue Type: Task Components: Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 As suggested by Igor Galic in TS-2335, to avoid namespace pollution, we could move move the old Lua plugin to plugins/deprecated, and name this one lua again from the start. From what I gather, the consensus on the mailing list was to replace the old plugin with this one. Given that the old plugin was experimental, and we've decided that all bets regarding compatibility and stability are off in experimental, I'm fairly certain we can just do that. I'd move it, for easy reference into plugins/deprecated, remove it from the build, and once the new plugin has absorbed all of its features, remove it all together. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2844) Documentation Update for ESI plugin
[ https://issues.apache.org/jira/browse/TS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008302#comment-14008302 ] ASF subversion and git services commented on TS-2844: - Commit 0896896aac9e402777dc72cf0e19f1bcf0681e16 in trafficserver's branch refs/heads/master from [~kichan] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0896896 ] TS-2844: Documentation update for esi plugin Documentation Update for ESI plugin --- Key: TS-2844 URL: https://issues.apache.org/jira/browse/TS-2844 Project: Traffic Server Issue Type: Task Components: Documentation, Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 Need to update the documentation for ESI Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (TS-2844) Documentation Update for ESI plugin
[ https://issues.apache.org/jira/browse/TS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan resolved TS-2844. -- Resolution: Fixed Documentation Update for ESI plugin --- Key: TS-2844 URL: https://issues.apache.org/jira/browse/TS-2844 Project: Traffic Server Issue Type: Task Components: Documentation, Plugins Reporter: Kit Chan Assignee: Kit Chan Fix For: 5.0.0 Need to update the documentation for ESI Plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2841) ReadTheDocs mixes HTTP URLs in with HTTPS
[
https://issues.apache.org/jira/browse/TS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008304#comment-14008304
]
Masakazu Kitajo commented on TS-2841:
-
Another URL for RTD's API is not configurable, but it would be fixed soon
because it seems just a regression.
https://github.com/rtfd/readthedocs.org/issues/830
ReadTheDocs mixes HTTP URLs in with HTTPS
-
Key: TS-2841
URL: https://issues.apache.org/jira/browse/TS-2841
Project: Traffic Server
Issue Type: Bug
Components: Documentation
Reporter: Leif Hedstrom
At least one place I found is:
{code}
script type=text/javascript
src=http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML;/script
{code}
I don't know how to modify this, but it would be great if this can be changed
to HTTPS. Also, I've made a copy of that file, and it's also available from
https://docs.trafficserver.apache.org/__RTD/MathJax.js
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2845) Commit e6b9cb533 causes problems with stats_over_http
[
https://issues.apache.org/jira/browse/TS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2845:
--
Priority: Critical (was: Major)
Commit e6b9cb533 causes problems with stats_over_http
-
Key: TS-2845
URL: https://issues.apache.org/jira/browse/TS-2845
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
Priority: Critical
Fix For: 5.0.0
After TS-2559, stats_over_http generates errors like
{code}
1400988784.563 2 192.168.201.14 ERR_READ_ERROR/200 21840 GET
http://loki.ogre.com/stat - DIRECT/loki.ogre.com text/javascript
1400988785.412 0 192.168.201.14 ERR_READ_ERROR/200 24152 GET
http://loki.ogre.com/stat - DIRECT/loki.ogre.com text/javascript
{code}
I have not investigated what the root cause is, but I know it started after
this commit (git bisect )
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (TS-2845) Commit e6b9cb533 causes problems with stats_over_http
Leif Hedstrom created TS-2845:
-
Summary: Commit e6b9cb533 causes problems with stats_over_http
Key: TS-2845
URL: https://issues.apache.org/jira/browse/TS-2845
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
After TS-2559, stats_over_http generates errors like
{code}
1400988784.563 2 192.168.201.14 ERR_READ_ERROR/200 21840 GET
http://loki.ogre.com/stat - DIRECT/loki.ogre.com text/javascript
1400988785.412 0 192.168.201.14 ERR_READ_ERROR/200 24152 GET
http://loki.ogre.com/stat - DIRECT/loki.ogre.com text/javascript
{code}
I have not investigated what the root cause is, but I know it started after
this commit (git bisect )
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2845) Commit e6b9cb533 causes problems with stats_over_http
[
https://issues.apache.org/jira/browse/TS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2845:
--
Fix Version/s: 5.0.0
Commit e6b9cb533 causes problems with stats_over_http
-
Key: TS-2845
URL: https://issues.apache.org/jira/browse/TS-2845
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
Priority: Critical
Fix For: 5.0.0
After TS-2559, stats_over_http generates errors like
{code}
1400988784.563 2 192.168.201.14 ERR_READ_ERROR/200 21840 GET
http://loki.ogre.com/stat - DIRECT/loki.ogre.com text/javascript
1400988785.412 0 192.168.201.14 ERR_READ_ERROR/200 24152 GET
http://loki.ogre.com/stat - DIRECT/loki.ogre.com text/javascript
{code}
I have not investigated what the root cause is, but I know it started after
this commit (git bisect )
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (TS-2846) Server pool selection for FQDN only frequently does not find valid entries.
Alan M. Carroll created TS-2846: --- Summary: Server pool selection for FQDN only frequently does not find valid entries. Key: TS-2846 URL: https://issues.apache.org/jira/browse/TS-2846 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Alan M. Carroll The logic for find server sessions in the server pool will generally not find entries that should be valid when the configuration is set to select by FQDN only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2846) Server pool selection for FQDN only frequently does not find valid entries.
[ https://issues.apache.org/jira/browse/TS-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll reassigned TS-2846: --- Assignee: Alan M. Carroll Server pool selection for FQDN only frequently does not find valid entries. --- Key: TS-2846 URL: https://issues.apache.org/jira/browse/TS-2846 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Alan M. Carroll Assignee: Alan M. Carroll The logic for find server sessions in the server pool will generally not find entries that should be valid when the configuration is set to select by FQDN only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2846) Server pool selection for FQDN only frequently does not find valid entries.
[ https://issues.apache.org/jira/browse/TS-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll updated TS-2846: Priority: Minor (was: Major) Server pool selection for FQDN only frequently does not find valid entries. --- Key: TS-2846 URL: https://issues.apache.org/jira/browse/TS-2846 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor The logic for find server sessions in the server pool will generally not find entries that should be valid when the configuration is set to select by FQDN only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008477#comment-14008477 ] Ethan Lai commented on TS-2344: --- [~bcall] It seems the proxy/config/body_factory/default/redirect#moved_permanently response file is not added, please commit this file as well. (Copied from proxy/config/body_factory/default/redirect#moved_temporary) :) 404 error was logged while url redirect request was processed corrctly -- Key: TS-2344 URL: https://issues.apache.org/jira/browse/TS-2344 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Eddie Assignee: Bryan Call Labels: Review Fix For: 5.0.0 Attachments: no_redirect_after_map.patch I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly and I could see the expected response in log as below: 2013-11-08 18:23:37 IP 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed in the error log too, which generates a lot of error logs (log rotation configured) and filling up disk space pretty fast. 20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly I could see the expected response in log as well: 2013-11-08 18:23:37 IP 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed too: 20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG proxy.config.log.extended_log_enabled INT 0 CONFIG proxy.config.log.extended_log_is_ascii INT 0 CONFIG proxy.config.log.extended_log_name STRING extended CONFIG proxy.config.log.extended_log_header STRING NULL CONFIG proxy.config.log.extended2_log_enabled INT 0 CONFIG proxy.config.log.extended2_log_is_ascii INT 1 CONFIG proxy.config.log.extended2_log_name STRING extended2 CONFIG proxy.config.log.extended2_log_header STRING NULL CONFIG proxy.config.log.separate_icp_logs INT 0 CONFIG proxy.config.log.separate_host_logs INT 0 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG proxy.config.log.extended_log_enabled INT 0 CONFIG proxy.config.log.extended_log_is_ascii INT 0 CONFIG
[jira] [Updated] (TS-2344) 404 error was logged while url redirect request was processed correctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-2344: --- Summary: 404 error was logged while url redirect request was processed correctly (was: 404 error was logged while url redirect request was processed corrctly) 404 error was logged while url redirect request was processed correctly --- Key: TS-2344 URL: https://issues.apache.org/jira/browse/TS-2344 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Eddie Assignee: Bryan Call Labels: Review Fix For: 5.0.0 Attachments: no_redirect_after_map.patch I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly and I could see the expected response in log as below: 2013-11-08 18:23:37 IP 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed in the error log too, which generates a lot of error logs (log rotation configured) and filling up disk space pretty fast. 20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly I could see the expected response in log as well: 2013-11-08 18:23:37 IP 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed too: 20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG proxy.config.log.extended_log_enabled INT 0 CONFIG proxy.config.log.extended_log_is_ascii INT 0 CONFIG proxy.config.log.extended_log_name STRING extended CONFIG proxy.config.log.extended_log_header STRING NULL CONFIG proxy.config.log.extended2_log_enabled INT 0 CONFIG proxy.config.log.extended2_log_is_ascii INT 1 CONFIG proxy.config.log.extended2_log_name STRING extended2 CONFIG proxy.config.log.extended2_log_header STRING NULL CONFIG proxy.config.log.separate_icp_logs INT 0 CONFIG proxy.config.log.separate_host_logs INT 0 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG proxy.config.log.extended_log_enabled INT 0 CONFIG proxy.config.log.extended_log_is_ascii INT 0 CONFIG proxy.config.log.extended_log_name STRING extended CONFIG proxy.config.log.extended_log_header STRING NULL CONFIG
[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed correctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008478#comment-14008478 ] ASF subversion and git services commented on TS-2344: - Commit 0c5012028577f7326b3f89eb505759ab454ab00f in trafficserver's branch refs/heads/master from [~yzlai] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0c50120 ] TS-2344: 404 error was logged while url redirect request was processed correctly Added missing file 404 error was logged while url redirect request was processed correctly --- Key: TS-2344 URL: https://issues.apache.org/jira/browse/TS-2344 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Eddie Assignee: Bryan Call Labels: Review Fix For: 5.0.0 Attachments: no_redirect_after_map.patch I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly and I could see the expected response in log as below: 2013-11-08 18:23:37 IP 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed in the error log too, which generates a lot of error logs (log rotation configured) and filling up disk space pretty fast. 20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly I could see the expected response in log as well: 2013-11-08 18:23:37 IP 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed too: 20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG proxy.config.log.extended_log_enabled INT 0 CONFIG proxy.config.log.extended_log_is_ascii INT 0 CONFIG proxy.config.log.extended_log_name STRING extended CONFIG proxy.config.log.extended_log_header STRING NULL CONFIG proxy.config.log.extended2_log_enabled INT 0 CONFIG proxy.config.log.extended2_log_is_ascii INT 1 CONFIG proxy.config.log.extended2_log_name STRING extended2 CONFIG proxy.config.log.extended2_log_header STRING NULL CONFIG proxy.config.log.separate_icp_logs INT 0 CONFIG proxy.config.log.separate_host_logs INT 0 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG
[jira] [Commented] (TS-2846) Server pool selection for FQDN only frequently does not find valid entries.
[ https://issues.apache.org/jira/browse/TS-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008547#comment-14008547 ] Leif Hedstrom commented on TS-2846: --- Is this for 5.0.0 ? Server pool selection for FQDN only frequently does not find valid entries. --- Key: TS-2846 URL: https://issues.apache.org/jira/browse/TS-2846 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor The logic for find server sessions in the server pool will generally not find entries that should be valid when the configuration is set to select by FQDN only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2825) Segmentation fault on POST request transformation
[
https://issues.apache.org/jira/browse/TS-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2825:
--
Assignee: Kit Chan
Segmentation fault on POST request transformation
-
Key: TS-2825
URL: https://issues.apache.org/jira/browse/TS-2825
Project: Traffic Server
Issue Type: Bug
Components: Core, HTTP, Lua, Plugins, TS API
Reporter: Pasquale Puzio
Assignee: Kit Chan
Priority: Critical
I'm trying to write a simple encryption/decryption plugin for Apache Traffic
Server. The plugin should transform requests/responses in order to
encrypt/decrypt them. I decided to write the plugin in LUA (using the ts-lua
plugin available here https://github.com/portl4t/ts-lua)
function encrypt(data, eos)
if (data == '') then
return data, eos
end
if (eos == 1) then
ts.debug('End of Stream')
end
return data, eos
end
function do_remap()
ts.debug('do_remap')
if (ts.client_request.get_method() == 'POST') then
ts.hook(TS_LUA_REQUEST_TRANSFORM, encrypt)
end
ts.http.resp_cache_transformed(0)
ts.http.resp_cache_untransformed(0)
return 0
end
Everything works fine for GET and DELETE requests, but when I send a POST
chunked-encoded request, ATS crashes almost every time.
if I don't activate the request transformation hook, the chunked request is
forwarded perfectly. Most of the time, if one request is forwarded
succesfully, the one after crashes.
Here is the stack trace:
[May 20 13:16:28.105] Server {0x7f045a1c1700} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[May 20 13:16:28.105] Server {0x7f045a1c1700} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
NOTE: Traffic Server received Sig 11: Segmentation fault
bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f045cd29cb0]
bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x171)[0x5c274f]
bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x883)[0x5c24cf]
bin/traffic_server(_ZN6HttpSM23do_api_callout_internalEv+0x1b7)[0x5ceaef]
bin/traffic_server(_ZN6HttpSM14do_api_calloutEv+0x26)[0x5dc18e]
bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x12f9)[0x5d6a19]
bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x1ba)[0x5d5718]
bin/traffic_server(_ZN6HttpSM36state_common_wait_for_transform_readEP17HttpTransformInfoMS_FiiPvEiS2_+0x39b)[0x5c1a11]
bin/traffic_server(_ZN6HttpSM37state_request_wait_for_transform_readEiPv+0x1e1)[0x5c1483]
bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0x333)[0x5c5eeb]
bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x68)[0x4f06b2]
bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x2f6)[0x538d2a]
bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x68)[0x4f06b2]
bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x11e)[0x7537e2]
bin/traffic_server(_ZN7EThread7executeEv+0xc9)[0x753a27]
bin/traffic_server[0x752ca7]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f045cd21e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f045c0383fd]
Segmentation fault (core dumped)
I've already tried to use one of the example plugins for request
transformation and I still have the same problem. The only way to make the
problem disappear is to avoid request transformation.
Is there something wrong in the way I'm transforming requests? What does this
segmentation fault depend on?
Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2819) Add configuration and APIs to disable loop detection
[ https://issues.apache.org/jira/browse/TS-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008550#comment-14008550 ] Leif Hedstrom commented on TS-2819: --- Setting to sometime for now Add configuration and APIs to disable loop detection Key: TS-2819 URL: https://issues.apache.org/jira/browse/TS-2819 Project: Traffic Server Issue Type: Improvement Components: Configuration, HTTP Reporter: Bryan Call Fix For: sometime -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2825) Segmentation fault on POST request transformation
[
https://issues.apache.org/jira/browse/TS-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008548#comment-14008548
]
Leif Hedstrom commented on TS-2825:
---
Setting to sometime for now, move to appropriate version after investigation.
Segmentation fault on POST request transformation
-
Key: TS-2825
URL: https://issues.apache.org/jira/browse/TS-2825
Project: Traffic Server
Issue Type: Bug
Components: Core, HTTP, Lua, Plugins, TS API
Reporter: Pasquale Puzio
Assignee: Kit Chan
Priority: Critical
Fix For: sometime
I'm trying to write a simple encryption/decryption plugin for Apache Traffic
Server. The plugin should transform requests/responses in order to
encrypt/decrypt them. I decided to write the plugin in LUA (using the ts-lua
plugin available here https://github.com/portl4t/ts-lua)
function encrypt(data, eos)
if (data == '') then
return data, eos
end
if (eos == 1) then
ts.debug('End of Stream')
end
return data, eos
end
function do_remap()
ts.debug('do_remap')
if (ts.client_request.get_method() == 'POST') then
ts.hook(TS_LUA_REQUEST_TRANSFORM, encrypt)
end
ts.http.resp_cache_transformed(0)
ts.http.resp_cache_untransformed(0)
return 0
end
Everything works fine for GET and DELETE requests, but when I send a POST
chunked-encoded request, ATS crashes almost every time.
if I don't activate the request transformation hook, the chunked request is
forwarded perfectly. Most of the time, if one request is forwarded
succesfully, the one after crashes.
Here is the stack trace:
[May 20 13:16:28.105] Server {0x7f045a1c1700} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[May 20 13:16:28.105] Server {0x7f045a1c1700} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
NOTE: Traffic Server received Sig 11: Segmentation fault
bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f045cd29cb0]
bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x171)[0x5c274f]
bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x883)[0x5c24cf]
bin/traffic_server(_ZN6HttpSM23do_api_callout_internalEv+0x1b7)[0x5ceaef]
bin/traffic_server(_ZN6HttpSM14do_api_calloutEv+0x26)[0x5dc18e]
bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x12f9)[0x5d6a19]
bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x1ba)[0x5d5718]
bin/traffic_server(_ZN6HttpSM36state_common_wait_for_transform_readEP17HttpTransformInfoMS_FiiPvEiS2_+0x39b)[0x5c1a11]
bin/traffic_server(_ZN6HttpSM37state_request_wait_for_transform_readEiPv+0x1e1)[0x5c1483]
bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0x333)[0x5c5eeb]
bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x68)[0x4f06b2]
bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x2f6)[0x538d2a]
bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x68)[0x4f06b2]
bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x11e)[0x7537e2]
bin/traffic_server(_ZN7EThread7executeEv+0xc9)[0x753a27]
bin/traffic_server[0x752ca7]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f045cd21e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f045c0383fd]
Segmentation fault (core dumped)
I've already tried to use one of the example plugins for request
transformation and I still have the same problem. The only way to make the
problem disappear is to avoid request transformation.
Is there something wrong in the way I'm transforming requests? What does this
segmentation fault depend on?
Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2812) header_normalize to convert lower case spdy hdrs to camel case for backward compatibility
[ https://issues.apache.org/jira/browse/TS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008551#comment-14008551 ] Leif Hedstrom commented on TS-2812: --- Is this for v5.0.0? header_normalize to convert lower case spdy hdrs to camel case for backward compatibility - Key: TS-2812 URL: https://issues.apache.org/jira/browse/TS-2812 Project: Traffic Server Issue Type: New Feature Components: SPDY Reporter: Sudheer Vinukonda Labels: spdy, yahoo Attachments: ts2812.diff During our SPDY testing, we observed that certain legacy systems are not able to handle lower case hdrs mandated by SPDY (and even http 1.0). This simple plugin converts the lowercase header names into camel case and could be used as an interim solution until the legacy systems are upgraded. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2825) Segmentation fault on POST request transformation
[
https://issues.apache.org/jira/browse/TS-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2825:
--
Fix Version/s: sometime
Segmentation fault on POST request transformation
-
Key: TS-2825
URL: https://issues.apache.org/jira/browse/TS-2825
Project: Traffic Server
Issue Type: Bug
Components: Core, HTTP, Lua, Plugins, TS API
Reporter: Pasquale Puzio
Assignee: Kit Chan
Priority: Critical
Fix For: sometime
I'm trying to write a simple encryption/decryption plugin for Apache Traffic
Server. The plugin should transform requests/responses in order to
encrypt/decrypt them. I decided to write the plugin in LUA (using the ts-lua
plugin available here https://github.com/portl4t/ts-lua)
function encrypt(data, eos)
if (data == '') then
return data, eos
end
if (eos == 1) then
ts.debug('End of Stream')
end
return data, eos
end
function do_remap()
ts.debug('do_remap')
if (ts.client_request.get_method() == 'POST') then
ts.hook(TS_LUA_REQUEST_TRANSFORM, encrypt)
end
ts.http.resp_cache_transformed(0)
ts.http.resp_cache_untransformed(0)
return 0
end
Everything works fine for GET and DELETE requests, but when I send a POST
chunked-encoded request, ATS crashes almost every time.
if I don't activate the request transformation hook, the chunked request is
forwarded perfectly. Most of the time, if one request is forwarded
succesfully, the one after crashes.
Here is the stack trace:
[May 20 13:16:28.105] Server {0x7f045a1c1700} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[May 20 13:16:28.105] Server {0x7f045a1c1700} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
NOTE: Traffic Server received Sig 11: Segmentation fault
bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f045cd29cb0]
bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x171)[0x5c274f]
bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x883)[0x5c24cf]
bin/traffic_server(_ZN6HttpSM23do_api_callout_internalEv+0x1b7)[0x5ceaef]
bin/traffic_server(_ZN6HttpSM14do_api_calloutEv+0x26)[0x5dc18e]
bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x12f9)[0x5d6a19]
bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x1ba)[0x5d5718]
bin/traffic_server(_ZN6HttpSM36state_common_wait_for_transform_readEP17HttpTransformInfoMS_FiiPvEiS2_+0x39b)[0x5c1a11]
bin/traffic_server(_ZN6HttpSM37state_request_wait_for_transform_readEiPv+0x1e1)[0x5c1483]
bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0x333)[0x5c5eeb]
bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x68)[0x4f06b2]
bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x2f6)[0x538d2a]
bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x68)[0x4f06b2]
bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x11e)[0x7537e2]
bin/traffic_server(_ZN7EThread7executeEv+0xc9)[0x753a27]
bin/traffic_server[0x752ca7]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f045cd21e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f045c0383fd]
Segmentation fault (core dumped)
I've already tried to use one of the example plugins for request
transformation and I still have the same problem. The only way to make the
problem disappear is to avoid request transformation.
Is there something wrong in the way I'm transforming requests? What does this
segmentation fault depend on?
Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2819) Add configuration and APIs to disable loop detection
[ https://issues.apache.org/jira/browse/TS-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2819: -- Fix Version/s: sometime Add configuration and APIs to disable loop detection Key: TS-2819 URL: https://issues.apache.org/jira/browse/TS-2819 Project: Traffic Server Issue Type: Improvement Components: Configuration, HTTP Reporter: Bryan Call Fix For: sometime -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2804) Add revalidation plugin
[ https://issues.apache.org/jira/browse/TS-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008549#comment-14008549 ] Leif Hedstrom commented on TS-2804: --- Is this for v5.0.0 ? Please mark Fix Version accordingly. Add revalidation plugin --- Key: TS-2804 URL: https://issues.apache.org/jira/browse/TS-2804 Project: Traffic Server Issue Type: New Feature Reporter: Phil Sorber Assignee: Phil Sorber We have developed a plugin that allows you to use regular expressions to force a revalidation of content. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2800) SPDY session (keep-alive) timeouts is too low and not configurable
[ https://issues.apache.org/jira/browse/TS-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2800: -- Fix Version/s: 5.0.0 SPDY session (keep-alive) timeouts is too low and not configurable Key: TS-2800 URL: https://issues.apache.org/jira/browse/TS-2800 Project: Traffic Server Issue Type: New Feature Components: SPDY Reporter: Leif Hedstrom Assignee: Bryan Call Fix For: 5.0.0 The default timeout on our SPDY sessions is way to short by default (30s), and also not configurable. I think we should 1. Create a new configuration (following our other timeout naming conventions) for SPDY inactivity / active timeouts. 2. Increase the defaults to be much higher. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2032) Create metrics for cache-lookup times
[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2032: -- Fix Version/s: sometime Create metrics for cache-lookup times - Key: TS-2032 URL: https://issues.apache.org/jira/browse/TS-2032 Project: Traffic Server Issue Type: New Feature Components: Metrics Reporter: Leif Hedstrom Fix For: sometime There was some plumbing for this in HttpSM.cc (grep for this bug #), but it was never used. I left the code uncommented, and we can maybe add this back later. It might also need a metric for the number of cache lookups done as well (not sure we have one). This is also related to TS-1820, where this was cleaned out. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2817) ATS crash in SSLNetVConnection::load_buffer_and_write
[
https://issues.apache.org/jira/browse/TS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2817:
--
Fix Version/s: 5.0.0
ATS crash in SSLNetVConnection::load_buffer_and_write
-
Key: TS-2817
URL: https://issues.apache.org/jira/browse/TS-2817
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Sudheer Vinukonda
Fix For: 5.0.0
Our production host running latest master crashed with the below stack
traces. Based on the stack traces, this might be related to a recent jira
TS-2815. On second thought, this may also be a duplicate of TS-2776.
{code}
[E. Mgmt] log == [TrafficManager] using root directory '/home/y'
[example_prep.sh] Checking/Moving old cores...
[TrafficServer] using root directory '/home/y'
NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x329720f500)[0x2b8c4da4f500]
/usr/lib64/libssl.so.10[0x331622b2e7]
/usr/lib64/libssl.so.10(ssl3_write_bytes+0x75)[0x331622b905]
/home/y/bin/traffic_server(_ZN17SSLNetVConnection21load_buffer_and_writeElRlS0_R17MIOBufferAccessorRi+0xdf)[0x6fbb6f]
/home/y/bin/traffic_server(_Z15write_to_net_ioP10NetHandlerP18UnixNetVConnectionP7EThread+0x368)[0x70f938]
/home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x283)[0x7046d3]
/home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x73278f]
/home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x733133]
/home/y/bin/traffic_server[0x731b3a]
/lib64/libpthread.so.0(+0x3297207851)[0x2b8c4da47851]
/lib64/libc.so.6(clone+0x6d)[0x3296ee890d]
[example_alarm_bin.sh] sent alarm: l10.ycs.sjb.yahoo.com [Sat May 17 20:13:29
2014] The TS-TM connection is broken for some reason. Either restart TS and TM
or correct this error for TM
to display TS statistics correctly
[E. Mgmt] log == [TrafficManager] using root directory '/home/y'
[example_prep.sh] Checking/Moving old cores...
[TrafficServer] using root directory '/home/y'
NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x329720f500)[0x2aed4fbcc500]
/lib64/libc.so.6(memcpy+0x15b)[0x3296e8997b]
/home/y/bin/traffic_server(_ZN9LogAccess11marshal_memEPcPKcii+0x2f)[0x60f11f]
/home/y/bin/traffic_server(_ZN13LogAccessHttp28marshal_client_req_url_canonEPc+0x20)[0x6114e0]
/home/y/bin/traffic_server(_ZN12LogFieldList7marshalEP9LogAccessPc+0x32)[0x61d1e2]
/home/y/bin/traffic_server(_ZN9LogObject3logEP9LogAccessPKc+0x319)[0x628ba9]
/home/y/bin/traffic_server(_ZN16LogObjectManager3logEP9LogAccess+0x5e)[0x6295be]
/home/y/bin/traffic_server(_ZN6HttpSM12update_statsEv+0x5d8)[0x599ce8]
/home/y/bin/traffic_server(_ZN6HttpSM9kill_thisEv+0x7a0)[0x5a4a40]
/home/y/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0x188)[0x5a4dc8]
/home/y/bin/traffic_server(_ZN10HttpTunnel12main_handlerEiPv+0xe0)[0x5e7050]
/home/y/bin/traffic_server[0x70d6f1]
/home/y/bin/traffic_server(_Z15write_to_net_ioP10NetHandlerP18UnixNetVConnectionP7EThread+0x95b)[0x70ff2b]
/home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x283)[0x7046d3]
/home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x73278f]
/home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x733133]
/home/y/bin/traffic_server[0x731b3a]
/lib64/libpthread.so.0(+0x3297207851)[0x2aed4fbc4851]
/lib64/libc.so.6(clone+0x6d)[0x3296ee890d]
[E. Mgmt] log == [TrafficManager] using root directory '/
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2800) SPDY session (keep-alive) timeouts is too low and not configurable
[ https://issues.apache.org/jira/browse/TS-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2800: -- Assignee: Bryan Call SPDY session (keep-alive) timeouts is too low and not configurable Key: TS-2800 URL: https://issues.apache.org/jira/browse/TS-2800 Project: Traffic Server Issue Type: New Feature Components: SPDY Reporter: Leif Hedstrom Assignee: Bryan Call Fix For: 5.0.0 The default timeout on our SPDY sessions is way to short by default (30s), and also not configurable. I think we should 1. Create a new configuration (following our other timeout naming conventions) for SPDY inactivity / active timeouts. 2. Increase the defaults to be much higher. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2832) Add links from an API description to the code for that object
[ https://issues.apache.org/jira/browse/TS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2832: -- Fix Version/s: Docs Add links from an API description to the code for that object - Key: TS-2832 URL: https://issues.apache.org/jira/browse/TS-2832 Project: Traffic Server Issue Type: Bug Reporter: Jack Bates Fix For: Docs Doxygen knows where in the code objects are located. This uses that info to add links from the documentation into the code. Based on the sphinx.ext.viewcode and sphinx.ext.linkcode extensions. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2032) Create metrics for cache-lookup times
[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2032: -- Assignee: (was: Leif Hedstrom) Create metrics for cache-lookup times - Key: TS-2032 URL: https://issues.apache.org/jira/browse/TS-2032 Project: Traffic Server Issue Type: New Feature Components: Metrics Reporter: Leif Hedstrom Fix For: sometime There was some plumbing for this in HttpSM.cc (grep for this bug #), but it was never used. I left the code uncommented, and we can maybe add this back later. It might also need a metric for the number of cache lookups done as well (not sure we have one). This is also related to TS-1820, where this was cleaned out. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2817) ATS crash in SSLNetVConnection::load_buffer_and_write
[
https://issues.apache.org/jira/browse/TS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008553#comment-14008553
]
Leif Hedstrom commented on TS-2817:
---
Do we need this for 5.0.0? I think so, so marking it as such.
ATS crash in SSLNetVConnection::load_buffer_and_write
-
Key: TS-2817
URL: https://issues.apache.org/jira/browse/TS-2817
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Sudheer Vinukonda
Fix For: 5.0.0
Our production host running latest master crashed with the below stack
traces. Based on the stack traces, this might be related to a recent jira
TS-2815. On second thought, this may also be a duplicate of TS-2776.
{code}
[E. Mgmt] log == [TrafficManager] using root directory '/home/y'
[example_prep.sh] Checking/Moving old cores...
[TrafficServer] using root directory '/home/y'
NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x329720f500)[0x2b8c4da4f500]
/usr/lib64/libssl.so.10[0x331622b2e7]
/usr/lib64/libssl.so.10(ssl3_write_bytes+0x75)[0x331622b905]
/home/y/bin/traffic_server(_ZN17SSLNetVConnection21load_buffer_and_writeElRlS0_R17MIOBufferAccessorRi+0xdf)[0x6fbb6f]
/home/y/bin/traffic_server(_Z15write_to_net_ioP10NetHandlerP18UnixNetVConnectionP7EThread+0x368)[0x70f938]
/home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x283)[0x7046d3]
/home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x73278f]
/home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x733133]
/home/y/bin/traffic_server[0x731b3a]
/lib64/libpthread.so.0(+0x3297207851)[0x2b8c4da47851]
/lib64/libc.so.6(clone+0x6d)[0x3296ee890d]
[example_alarm_bin.sh] sent alarm: l10.ycs.sjb.yahoo.com [Sat May 17 20:13:29
2014] The TS-TM connection is broken for some reason. Either restart TS and TM
or correct this error for TM
to display TS statistics correctly
[E. Mgmt] log == [TrafficManager] using root directory '/home/y'
[example_prep.sh] Checking/Moving old cores...
[TrafficServer] using root directory '/home/y'
NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x329720f500)[0x2aed4fbcc500]
/lib64/libc.so.6(memcpy+0x15b)[0x3296e8997b]
/home/y/bin/traffic_server(_ZN9LogAccess11marshal_memEPcPKcii+0x2f)[0x60f11f]
/home/y/bin/traffic_server(_ZN13LogAccessHttp28marshal_client_req_url_canonEPc+0x20)[0x6114e0]
/home/y/bin/traffic_server(_ZN12LogFieldList7marshalEP9LogAccessPc+0x32)[0x61d1e2]
/home/y/bin/traffic_server(_ZN9LogObject3logEP9LogAccessPKc+0x319)[0x628ba9]
/home/y/bin/traffic_server(_ZN16LogObjectManager3logEP9LogAccess+0x5e)[0x6295be]
/home/y/bin/traffic_server(_ZN6HttpSM12update_statsEv+0x5d8)[0x599ce8]
/home/y/bin/traffic_server(_ZN6HttpSM9kill_thisEv+0x7a0)[0x5a4a40]
/home/y/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0x188)[0x5a4dc8]
/home/y/bin/traffic_server(_ZN10HttpTunnel12main_handlerEiPv+0xe0)[0x5e7050]
/home/y/bin/traffic_server[0x70d6f1]
/home/y/bin/traffic_server(_Z15write_to_net_ioP10NetHandlerP18UnixNetVConnectionP7EThread+0x95b)[0x70ff2b]
/home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x283)[0x7046d3]
/home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x73278f]
/home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x733133]
/home/y/bin/traffic_server[0x731b3a]
/lib64/libpthread.so.0(+0x3297207851)[0x2aed4fbc4851]
/lib64/libc.so.6(clone+0x6d)[0x3296ee890d]
[E. Mgmt] log == [TrafficManager] using root directory '/
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (TS-2834) header_rewrite: internal transaction and client IP conditions
[ https://issues.apache.org/jira/browse/TS-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2834: - Assignee: Leif Hedstrom header_rewrite: internal transaction and client IP conditions - Key: TS-2834 URL: https://issues.apache.org/jira/browse/TS-2834 Project: Traffic Server Issue Type: Improvement Reporter: Manjesh Nilange Assignee: Leif Hedstrom Fix For: 5.0.0 It would be nice to use the above two conditions in the rules. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2836) TS attempt to connect to dead server at least once
[ https://issues.apache.org/jira/browse/TS-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2836: -- Fix Version/s: (was: sometime) 5.1.0 TS attempt to connect to dead server at least once -- Key: TS-2836 URL: https://issues.apache.org/jira/browse/TS-2836 Project: Traffic Server Issue Type: Bug Affects Versions: 4.0.2, 5.0.0 Reporter: Masakazu Kitajo Fix For: 5.1.0 Even if I set proxy.config.http.connect_attempts_max_retries_dead_server to 0, Traffic Server attempt to connect to dead server. || The configuration value || Number of times TS attempt to connect || | 0 | 1 | | 1 | 1 | | 2 | 2 | | 3 | 3 | -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2837) Dangling pointer in URLImpl which may cause core dump
[
https://issues.apache.org/jira/browse/TS-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008555#comment-14008555
]
Leif Hedstrom commented on TS-2837:
---
[~bcall] What do you think about this one? 5.0.0 or move out?
Dangling pointer in URLImpl which may cause core dump
-
Key: TS-2837
URL: https://issues.apache.org/jira/browse/TS-2837
Project: Traffic Server
Issue Type: Bug
Components: HTTP, Logging
Affects Versions: 4.0.2
Reporter: kang li
Labels: crash
There were core dump shows that URLImpl::m_ptr_printed_string was out of
bound.
{code}
#0 ink_strlcpy (dst=value optimized out, src=0x2b64901a79a4 Address
0x2b64901a79a4 out of bounds, siz=value optimized out)
at ink_string.cc:226
#1 0x0058d820 in LogAccessHttp::init (this=0x2b631752da20) at
LogAccessHttp.cc:96
#2 0x0058a96f in resolve_logfield_string (context=0x2b631752da20,
format_str=0x3468e10 !DOCTYPE html\nhtml lang=\en-us\head\nmeta
http-equiv=\content-type\ content=\text/html; charset=UTF-8\\nmeta
charset=\utf-8\\ntitleYahoo/title\nmeta name=\viewport\
content=\wid...) at LogAccess.cc:1396
#3 0x00508fed in HttpBodyTemplate::build_instantiated_buffer
(this=0x3468de0, context=value optimized out,
buflen_return=0x2b63e2c42068) at HttpBodyFactory.cc:1015
#4 0x00509ea4 in HttpBodyFactory::fabricate (this=value optimized
out, acpt_language_list=0x2b631752e130,
acpt_charset_list=0x2b631752dfd0, type=0x6d2c3d connect#failed_connect,
context=0x2b63e2c416d8, buffer_length_return=0x2b63e2c42068,
content_language_return=0x2b631752e2a8,
content_charset_return=0x2b631752e2a0, set_return=0x2b631752e298) at
HttpBodyFactory.cc:451
#5 0x0050b1b7 in HttpBodyFactory::fabricate_with_old_api(const char
*,
HttpTransact::State *, int64_t, int64_t *, char *, size_t, char *, size_t,
const char *, typedef __va_list_tag __va_list_tag *) (this=0x344e850,
type=0x6d2c3d connect#failed_connect,
context=0x2b63e2c416d8, max_buffer_length=8192,
resulting_buffer_length=0x2b63e2c42068,
content_language_out_buf=0x2b631752e460
en,
content_language_buf_size=256, content_type_out_buf=0x2b631752e360
text/html, content_type_buf_size=256,
format=0x6ce288 internal error - server connection terminated,
ap=0x2b631752e590) at HttpBodyFactory.cc:137
#6 0x0054cd74 in HttpTransact::build_error_response
(s=0x2b63e2c416d8,
status_code=HTTP_STATUS_BAD_GATEWAY,
reason_phrase_or_null=0x6ce288 internal error - server connection
terminated, error_body_type=value optimized out,
format=0x6ce288 internal error - server connection terminated) at
HttpTransact.cc:7998
#7 0x00551b42 in HttpTransact::handle_server_connection_not_open
(s=0x2b63e2c416d8) at HttpTransact.cc:3719
#8 0x00562f31 in HttpTransact::HandleResponse (s=0x2b63e2c416d8) at
HttpTransact.cc:3180
#9 0x0051c588 in HttpSM::call_transact_and_set_next_state
(this=0x2b63e2c41670, f=value optimized out) at HttpSM.cc:6817
#10 0x00531f89 in HttpSM::state_http_server_open (this=0x2b63e2c41670,
event=201, data=0xff9d) at HttpSM.cc:1712
#11 0x00530b38 in HttpSM::main_handler (this=0x2b63e2c41670,
event=201,
data=0xff9d) at HttpSM.cc:2548
#12 0x006878ec in handleEvent (this=0x2b64ac19f870, t=0x2b6315111010)
at ../../iocore/eventsystem/I_Continuation.h:146
#13 UnixNetVConnection::connectUp (this=0x2b64ac19f870, t=0x2b6315111010) at
UnixNetVConnection.cc:1104
#14 0x006849ca in UnixNetProcessor::connect_re_internal (this=value
optimized out, cont=value optimized out,
target=value optimized out, opt=0x2b631752f990) at
UnixNetProcessor.cc:250
#15 0x005314ae in connect_re (this=0x2b63e2c41670, raw=value
optimized
out) at ../../iocore/net/P_UnixNetProcessor.h:89
#16 HttpSM::do_http_server_open (this=0x2b63e2c41670, raw=value optimized
out) at HttpSM.cc:4676
#17 0x00536446 in HttpSM::set_next_state (this=0x2b63e2c41670) at
HttpSM.cc:7006
#18 0x005371ef in HttpSM::state_send_server_request_header
(this=0x2b63e2c41670, event=104, data=0x2b64144c7e28) at HttpSM.cc:2008
#19 0x00530b38 in HttpSM::main_handler (this=0x2b63e2c41670,
event=104,
data=0x2b64144c7e28) at HttpSM.cc:2548
#20 0x006872a1 in handleEvent (event=value optimized out,
nh=0x2b6315114e20, vc=0x2b64144c7d20)
at ../../iocore/eventsystem/I_Continuation.h:146
#21 read_signal_and_update (event=value optimized out, nh=0x2b6315114e20,
vc=0x2b64144c7d20) at UnixNetVConnection.cc:138
#22 read_signal_done (event=value optimized out, nh=0x2b6315114e20,
vc=0x2b64144c7d20) at UnixNetVConnection.cc:168
#23 0x00689ab6 in read_from_net
[jira] [Updated] (TS-2834) header_rewrite: internal transaction and client IP conditions
[ https://issues.apache.org/jira/browse/TS-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2834: -- Fix Version/s: 5.0.0 header_rewrite: internal transaction and client IP conditions - Key: TS-2834 URL: https://issues.apache.org/jira/browse/TS-2834 Project: Traffic Server Issue Type: Improvement Reporter: Manjesh Nilange Assignee: Leif Hedstrom Fix For: 5.0.0 It would be nice to use the above two conditions in the rules. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2837) Dangling pointer in URLImpl which may cause core dump
[
https://issues.apache.org/jira/browse/TS-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2837:
--
Labels: crash (was: )
Dangling pointer in URLImpl which may cause core dump
-
Key: TS-2837
URL: https://issues.apache.org/jira/browse/TS-2837
Project: Traffic Server
Issue Type: Bug
Components: HTTP, Logging
Affects Versions: 4.0.2
Reporter: kang li
Labels: crash
There were core dump shows that URLImpl::m_ptr_printed_string was out of
bound.
{code}
#0 ink_strlcpy (dst=value optimized out, src=0x2b64901a79a4 Address
0x2b64901a79a4 out of bounds, siz=value optimized out)
at ink_string.cc:226
#1 0x0058d820 in LogAccessHttp::init (this=0x2b631752da20) at
LogAccessHttp.cc:96
#2 0x0058a96f in resolve_logfield_string (context=0x2b631752da20,
format_str=0x3468e10 !DOCTYPE html\nhtml lang=\en-us\head\nmeta
http-equiv=\content-type\ content=\text/html; charset=UTF-8\\nmeta
charset=\utf-8\\ntitleYahoo/title\nmeta name=\viewport\
content=\wid...) at LogAccess.cc:1396
#3 0x00508fed in HttpBodyTemplate::build_instantiated_buffer
(this=0x3468de0, context=value optimized out,
buflen_return=0x2b63e2c42068) at HttpBodyFactory.cc:1015
#4 0x00509ea4 in HttpBodyFactory::fabricate (this=value optimized
out, acpt_language_list=0x2b631752e130,
acpt_charset_list=0x2b631752dfd0, type=0x6d2c3d connect#failed_connect,
context=0x2b63e2c416d8, buffer_length_return=0x2b63e2c42068,
content_language_return=0x2b631752e2a8,
content_charset_return=0x2b631752e2a0, set_return=0x2b631752e298) at
HttpBodyFactory.cc:451
#5 0x0050b1b7 in HttpBodyFactory::fabricate_with_old_api(const char
*,
HttpTransact::State *, int64_t, int64_t *, char *, size_t, char *, size_t,
const char *, typedef __va_list_tag __va_list_tag *) (this=0x344e850,
type=0x6d2c3d connect#failed_connect,
context=0x2b63e2c416d8, max_buffer_length=8192,
resulting_buffer_length=0x2b63e2c42068,
content_language_out_buf=0x2b631752e460
en,
content_language_buf_size=256, content_type_out_buf=0x2b631752e360
text/html, content_type_buf_size=256,
format=0x6ce288 internal error - server connection terminated,
ap=0x2b631752e590) at HttpBodyFactory.cc:137
#6 0x0054cd74 in HttpTransact::build_error_response
(s=0x2b63e2c416d8,
status_code=HTTP_STATUS_BAD_GATEWAY,
reason_phrase_or_null=0x6ce288 internal error - server connection
terminated, error_body_type=value optimized out,
format=0x6ce288 internal error - server connection terminated) at
HttpTransact.cc:7998
#7 0x00551b42 in HttpTransact::handle_server_connection_not_open
(s=0x2b63e2c416d8) at HttpTransact.cc:3719
#8 0x00562f31 in HttpTransact::HandleResponse (s=0x2b63e2c416d8) at
HttpTransact.cc:3180
#9 0x0051c588 in HttpSM::call_transact_and_set_next_state
(this=0x2b63e2c41670, f=value optimized out) at HttpSM.cc:6817
#10 0x00531f89 in HttpSM::state_http_server_open (this=0x2b63e2c41670,
event=201, data=0xff9d) at HttpSM.cc:1712
#11 0x00530b38 in HttpSM::main_handler (this=0x2b63e2c41670,
event=201,
data=0xff9d) at HttpSM.cc:2548
#12 0x006878ec in handleEvent (this=0x2b64ac19f870, t=0x2b6315111010)
at ../../iocore/eventsystem/I_Continuation.h:146
#13 UnixNetVConnection::connectUp (this=0x2b64ac19f870, t=0x2b6315111010) at
UnixNetVConnection.cc:1104
#14 0x006849ca in UnixNetProcessor::connect_re_internal (this=value
optimized out, cont=value optimized out,
target=value optimized out, opt=0x2b631752f990) at
UnixNetProcessor.cc:250
#15 0x005314ae in connect_re (this=0x2b63e2c41670, raw=value
optimized
out) at ../../iocore/net/P_UnixNetProcessor.h:89
#16 HttpSM::do_http_server_open (this=0x2b63e2c41670, raw=value optimized
out) at HttpSM.cc:4676
#17 0x00536446 in HttpSM::set_next_state (this=0x2b63e2c41670) at
HttpSM.cc:7006
#18 0x005371ef in HttpSM::state_send_server_request_header
(this=0x2b63e2c41670, event=104, data=0x2b64144c7e28) at HttpSM.cc:2008
#19 0x00530b38 in HttpSM::main_handler (this=0x2b63e2c41670,
event=104,
data=0x2b64144c7e28) at HttpSM.cc:2548
#20 0x006872a1 in handleEvent (event=value optimized out,
nh=0x2b6315114e20, vc=0x2b64144c7d20)
at ../../iocore/eventsystem/I_Continuation.h:146
#21 read_signal_and_update (event=value optimized out, nh=0x2b6315114e20,
vc=0x2b64144c7d20) at UnixNetVConnection.cc:138
#22 read_signal_done (event=value optimized out, nh=0x2b6315114e20,
vc=0x2b64144c7d20) at UnixNetVConnection.cc:168
#23 0x00689ab6 in read_from_net (nh=0x2b6315114e20, vc=0x2b64144c7d20,
thread=value optimized out) at UnixNetVConnection.cc:291
#24
[jira] [Updated] (TS-2836) TS attempt to connect to dead server at least once
[ https://issues.apache.org/jira/browse/TS-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2836: -- Fix Version/s: sometime TS attempt to connect to dead server at least once -- Key: TS-2836 URL: https://issues.apache.org/jira/browse/TS-2836 Project: Traffic Server Issue Type: Bug Affects Versions: 4.0.2, 5.0.0 Reporter: Masakazu Kitajo Fix For: 5.1.0 Even if I set proxy.config.http.connect_attempts_max_retries_dead_server to 0, Traffic Server attempt to connect to dead server. || The configuration value || Number of times TS attempt to connect || | 0 | 1 | | 1 | 1 | | 2 | 2 | | 3 | 3 | -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2842) Can't set SPDY inactivity timeout with traffic_line
[
https://issues.apache.org/jira/browse/TS-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008559#comment-14008559
]
Leif Hedstrom commented on TS-2842:
---
Sounds like we need this for 5.0.0?
Can't set SPDY inactivity timeout with traffic_line
---
Key: TS-2842
URL: https://issues.apache.org/jira/browse/TS-2842
Project: Traffic Server
Issue Type: Bug
Components: SPDY, Tools
Reporter: Bryan Call
Fix For: 5.0.0
Works for other configuration options:
{code}
[bcall@l10 trafficserver]$ sudo traffic_line -s
proxy.config.http.keep_alive_no_activity_timeout_in -v 61
[bcall@l10 trafficserver]$ sudo traffic_line -r
proxy.config.http.keep_alive_no_activity_timeout_in
61
{code}
Doesn't work for the SPDY inactivity:
{code}
[bcall@l10 trafficserver]$ sudo traffic_line -s
proxy.config.spdy.no_activity_timeout_in -v 31
traffic_line: Please correct your variable name and|or value
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2843) Buffer overflow in SSL error messages
[
https://issues.apache.org/jira/browse/TS-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2843:
--
Fix Version/s: 5.0.0
Buffer overflow in SSL error messages
-
Key: TS-2843
URL: https://issues.apache.org/jira/browse/TS-2843
Project: Traffic Server
Issue Type: Bug
Components: SSL
Reporter: Leif Hedstrom
Fix For: 5.0.0
With a bad TLS config, I was getting the following errors, which looks like
it's reading buffers beyond EOL.
{code}
May 24 22:31:55 ats-int traffic_server[12696]: {0x2b89afcc6900} ERROR:
SSLUtils.cc:971 (SSLInitServerContext)
SSL::47870359922944:error:06065064:digital envelope
routines:EVP_DecryptFinal_ex:bad decrypt:evp_enc.c:596���
May 24 22:31:55 ats-int traffic_server[12696]: {0x2b89afcc6900} ERROR:
SSLUtils.cc:971 (SSLInitServerContext)
SSL::47870359922944:error:0906A065:PEM routines:PEM_do_header:bad
decrypt:pem_lib.c:483���
May 24 22:31:55 ats-int traffic_server[12696]: {0x2b89afcc6900} ERROR:
SSLUtils.cc:971 (SSLInitServerContext)
SSL::47870359922944:error:140B0009:SSL
routines:SSL_CTX_use_PrivateKey_file:PEM lib:ssl_rsa.c:669���
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2842) Can't set SPDY inactivity timeout with traffic_line
[
https://issues.apache.org/jira/browse/TS-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2842:
--
Fix Version/s: 5.0.0
Can't set SPDY inactivity timeout with traffic_line
---
Key: TS-2842
URL: https://issues.apache.org/jira/browse/TS-2842
Project: Traffic Server
Issue Type: Bug
Components: SPDY, Tools
Reporter: Bryan Call
Fix For: 5.0.0
Works for other configuration options:
{code}
[bcall@l10 trafficserver]$ sudo traffic_line -s
proxy.config.http.keep_alive_no_activity_timeout_in -v 61
[bcall@l10 trafficserver]$ sudo traffic_line -r
proxy.config.http.keep_alive_no_activity_timeout_in
61
{code}
Doesn't work for the SPDY inactivity:
{code}
[bcall@l10 trafficserver]$ sudo traffic_line -s
proxy.config.spdy.no_activity_timeout_in -v 31
traffic_line: Please correct your variable name and|or value
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2839) tsxs doesn't work on OSX
[
https://issues.apache.org/jira/browse/TS-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008558#comment-14008558
]
Leif Hedstrom commented on TS-2839:
---
Should we land it like this, or can we expect a second patch?
tsxs doesn't work on OSX
Key: TS-2839
URL: https://issues.apache.org/jira/browse/TS-2839
Project: Traffic Server
Issue Type: Improvement
Components: Tools
Reporter: Masakazu Kitajo
Fix For: 5.0.0
When I specify -L option to tsxs on OS X, I get these error messages below.
{noformat}
$ tsxs -L/somewhere/lib -o test.so test.cc
compiling test.cc - test.lo
linking - test.so
ld: warning: directory not found for option '-L/somewhere/lib'
ld: unknown option: --rpath=/somewhere/lib
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
tsxs: link failed: cc -bundle -flat_namespace -undefined suppress
-L/somewhere/lib -Wl,--rpath=/somewhere/lib -o test.so test.lo
{noformat}
It seems that two dashes and a equal sign for rpath are not supported on OS
X's ld.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2839) tsxs doesn't work on OSX
[
https://issues.apache.org/jira/browse/TS-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2839:
--
Fix Version/s: 5.0.0
tsxs doesn't work on OSX
Key: TS-2839
URL: https://issues.apache.org/jira/browse/TS-2839
Project: Traffic Server
Issue Type: Improvement
Components: Tools
Reporter: Masakazu Kitajo
Fix For: 5.0.0
When I specify -L option to tsxs on OS X, I get these error messages below.
{noformat}
$ tsxs -L/somewhere/lib -o test.so test.cc
compiling test.cc - test.lo
linking - test.so
ld: warning: directory not found for option '-L/somewhere/lib'
ld: unknown option: --rpath=/somewhere/lib
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
tsxs: link failed: cc -bundle -flat_namespace -undefined suppress
-L/somewhere/lib -Wl,--rpath=/somewhere/lib -o test.so test.lo
{noformat}
It seems that two dashes and a equal sign for rpath are not supported on OS
X's ld.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
