[jira] [Updated] (TS-1154) quick_filter on HEAD does not work
[ https://issues.apache.org/jira/browse/TS-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-1154: --- Attachment: head_method.diff quick_filter on HEAD does not work -- Key: TS-1154 URL: https://issues.apache.org/jira/browse/TS-1154 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Zhao Yongming Assignee: weijin Attachments: head_method.diff we take quick filter as a good solution for some security concern, but when I set it to 0x0733, it does not allow HEAD in, but setting as 0x0723 does that. Weijin have the patch in our tree: https://gitorious.org/trafficserver/taobao/commit/cb23b87d167da4074e047fabc94786003ee94e9a/diffs/db7d0e5be69988b531e8d1e4eea717e6d46df5cd I will commit if no one complain in 2 days. -- 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-1154) quick_filter on HEAD does not work
[ https://issues.apache.org/jira/browse/TS-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233303#comment-13233303 ] weijin commented on TS-1154: We found the the order of http methods in _hdrtoken_strs is not match the order in proxy.config.http.quick_filter.mask, so I changed the methods order in _hdrtoken_strs as the same order of the config comments. I am sure TS-1140 fix this problem, if jMCg will not back port TS-1140 on 3.0.x, maybe it need this patch in short term way. quick_filter on HEAD does not work -- Key: TS-1154 URL: https://issues.apache.org/jira/browse/TS-1154 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Zhao Yongming Assignee: weijin Attachments: head_method.diff we take quick filter as a good solution for some security concern, but when I set it to 0x0733, it does not allow HEAD in, but setting as 0x0723 does that. Weijin have the patch in our tree: https://gitorious.org/trafficserver/taobao/commit/cb23b87d167da4074e047fabc94786003ee94e9a/diffs/db7d0e5be69988b531e8d1e4eea717e6d46df5cd I will commit if no one complain in 2 days. -- 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-1152) http_ui error,when i get http://localhost/cache/
[
https://issues.apache.org/jira/browse/TS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233406#comment-13233406
]
Leif Hedstrom commented on TS-1152:
---
Yes, the WebUI itself is dead and gone (and it won't be missed). What's
somewhat confusing (and part of what makes it difficult to remove all remnants
of the UI), is that the setting also controls various internal stats pages.
To enable stats pages (e.g. the cache inspector), you should set records.config
to e.g.
{code}
CONFIG proxy.config.http_ui_enabled INT 3
{code}
This should be properly documented I'm fairly certain ;). With this, you can
now add remap rules (probably with specific ACLs), to add support for the
various stats pages. E.g.
{code}
map https://www.ogre.com/__pimp_my_cache/ http://{cache}/ @src_ip=192.168.1.1
@action=allow
{code}
I'm not sure why we get those errors and warnings above though, we should keep
this bug open, and fix that (assuming they show up with just the setting above).
http_ui error,when i get http://localhost/cache/
Key: TS-1152
URL: https://issues.apache.org/jira/browse/TS-1152
Project: Traffic Server
Issue Type: Bug
Components: Web UI
Affects Versions: 3.0.4
Environment: centos 6 x86_64
Reporter: bettydramit
When i enable http_ui ，I got follow error (get http://xxx.xxx.xxx.xxx/cache/)
[Mar 19 16:46:17.778] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:17.778] Manager {13989191624} ERROR: (last system error
11: Resource temporarily unavailable)
[Mar 19 16:46:19.089] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:19.090] Manager {13989191624} ERROR: (last system error
11: Resource temporarily unavailable)
[Mar 19 16:46:20.763] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:20.763] Manager {13989191624} ERROR: (last system error
11: Resource temporarily unavailable)
[Mar 19 16:58:21.906] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /robots.txt not valid autoconf file
[Mar 19 16:58:21.906] Manager {13989191624} ERROR: (last system error
11: Resource temporarily unavailable)
[Mar 19 17:01:43.703] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 17:01:43.703] Manager {13989191624} ERROR: (last system error
11: Resource temporarily unavailable)
--
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-1154) quick_filter on HEAD does not work
[ https://issues.apache.org/jira/browse/TS-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233407#comment-13233407 ] Leif Hedstrom commented on TS-1154: --- Yeah, I'd suggest just fixing this for 3.0.4 honestly. quick_filter on HEAD does not work -- Key: TS-1154 URL: https://issues.apache.org/jira/browse/TS-1154 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Zhao Yongming Assignee: weijin Attachments: head_method.diff we take quick filter as a good solution for some security concern, but when I set it to 0x0733, it does not allow HEAD in, but setting as 0x0723 does that. Weijin have the patch in our tree: https://gitorious.org/trafficserver/taobao/commit/cb23b87d167da4074e047fabc94786003ee94e9a/diffs/db7d0e5be69988b531e8d1e4eea717e6d46df5cd I will commit if no one complain in 2 days. -- 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-1157) freelist for TSAPI's and plugin structs
freelist for TSAPI's and plugin structs - Key: TS-1157 URL: https://issues.apache.org/jira/browse/TS-1157 Project: Traffic Server Issue Type: New Feature Components: TS API Reporter: Leif Hedstrom Fix For: 3.3.0 It could be useful to expose a simple freelist APIs, which lets plugins allocate and free simple C structs on a freelist, instead of having to call TSmalloc / TSfree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1114) Crash report: HttpTransactCache::SelectFromAlternates
[
https://issues.apache.org/jira/browse/TS-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak updated TS-1114:
-
Backport to Version: 3.0.4
Crash report: HttpTransactCache::SelectFromAlternates
-
Key: TS-1114
URL: https://issues.apache.org/jira/browse/TS-1114
Project: Traffic Server
Issue Type: Bug
Reporter: Zhao Yongming
Assignee: weijin
Fix For: 3.1.4
Attachments: cache_crash.diff
it may or may not be the upstream issue, let us open it for tracking.
{code}
#0 0x0053075e in HttpTransactCache::SelectFromAlternates
(cache_vector=0x2aaab80ff500, client_request=0x2aaab80ff4c0,
http_config_params=0x2aaab547b800) at ../../proxy/hdrs/HTTP.h:1375
1375((int32_t *) val)[0] = m_alt-m_object_key[0];
{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-1158) Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent
Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent Key: TS-1158 URL: https://issues.apache.org/jira/browse/TS-1158 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.0.3 Environment: ALL Reporter: John Plevyak Assignee: John Plevyak Fix For: 3.1.4 Because of the way session management works, the vio.mutex must be re-verified to be identical to the one the lock was taken on after the lock is acquired. Otherwise there is a race when the mutex is switched allowing such that the old lock is held while the new lock is in not held. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1158) Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent
[ https://issues.apache.org/jira/browse/TS-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Plevyak updated TS-1158: - Attachment: ts-1158-jp1.patch Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent Key: TS-1158 URL: https://issues.apache.org/jira/browse/TS-1158 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.0.3 Environment: ALL Reporter: John Plevyak Assignee: John Plevyak Fix For: 3.1.4 Attachments: ts-1158-jp1.patch Because of the way session management works, the vio.mutex must be re-verified to be identical to the one the lock was taken on after the lock is acquired. Otherwise there is a race when the mutex is switched allowing such that the old lock is held while the new lock is in not held. -- 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-1159) add compiler hints to debug logging
add compiler hints to debug logging --- Key: TS-1159 URL: https://issues.apache.org/jira/browse/TS-1159 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: James Peach Assignee: James Peach Priority: Minor Fix For: 3.1.4 Add compiler hints to specify that we usually don't emit diagnostic logging. -- 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-1159) add compiler hints to debug logging
[ https://issues.apache.org/jira/browse/TS-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-1159. - Resolution: Fixed 33770526cb4dd2bc7002d905e60b326880639fe1 TS-1159: add compiler hints to debug logging add compiler hints to debug logging --- Key: TS-1159 URL: https://issues.apache.org/jira/browse/TS-1159 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: James Peach Assignee: James Peach Priority: Minor Fix For: 3.1.4 Add compiler hints to specify that we usually don't emit diagnostic logging. -- 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
