[jira] Closed: (TS-36) Build: make install target should create '$(pkgsysconfdir)/internal' directory

[ https://issues.apache.org/jira/browse/TS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Paul closed TS-36. - Resolution: Fixed Fix Version/s: 2.0a Assignee: George Paul This is covered by TS-6 -George > Build:

[jira] Resolved: (TS-52) traffic_cop does not start

[ https://issues.apache.org/jira/browse/TS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-52. - Resolution: Fixed Committed. Thanks George! > traffic_cop does not start > -- > >

[jira] Updated: (TS-91) Traffic Manager starts up with WebUI disabled

[ https://issues.apache.org/jira/browse/TS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Paul updated TS-91: -- Component/s: (was: Console) WebUI > Traffic Manager starts up with WebUI disabled > ---

[jira] Created: (TS-91) Traffic Manager starts up with WebUI disabled

Traffic Manager starts up with WebUI disabled - Key: TS-91 URL: https://issues.apache.org/jira/browse/TS-91 Project: Traffic Server Issue Type: Bug Components: Console Affects Version

[jira] Created: (TS-90) Filter generator failing

Filter generator failing Key: TS-90 URL: https://issues.apache.org/jira/browse/TS-90 Project: Traffic Server Issue Type: Improvement Components: Config Reporter: Leif Hedstrom At startup, we g

[jira] Created: (TS-89) NNTP remnants

NNTP remnants - Key: TS-89 URL: https://issues.apache.org/jira/browse/TS-89 Project: Traffic Server Issue Type: Improvement Affects Versions: 2.0a Reporter: Leif Hedstrom Priority: Minor There are st

[jira] Created: (TS-88) traffic_server not able to setrlimit > 1024 on FDs

traffic_server not able to setrlimit > 1024 on FDs -- Key: TS-88 URL: https://issues.apache.org/jira/browse/TS-88 Project: Traffic Server Issue Type: Bug Components: Core Affects

[jira] Updated: (TS-18) IPv6 support

[ https://issues.apache.org/jira/browse/TS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsunayoshi Egawa updated TS-18: --- Attachment: trafficserver_ipv6.patch - Fuctions: 1. receive a request based on v4 and v6 - back pos

[jira] Resolved: (TS-6) traffic_manager does not start

[ https://issues.apache.org/jira/browse/TS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-6. Resolution: Fixed Committed, thanks George. > traffic_manager does not start > -- >

[jira] Updated: (TS-6) traffic_manager does not start

[ https://issues.apache.org/jira/browse/TS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Paul updated TS-6: - Attachment: TS-6_traffic_manager_patch4.diff Last patch was prepared a little to quickly :-( This updated patch replac

How to parse cookies via REQUEST_HDR_HOOK

Hello, I am trying to parse cookies via INK_HTTP_READ_REQUEST_HDR_HOOK. Upon callback, I can read field name (Cookie) via INKMimeHdrFieldNameGet but INKMimeHdrFieldValueStringGet for that field index returns NULL for char* and zero for size. Are there other ways to parse cookies as plug-in?

[jira] Commented: (TS-80) Support regular expressions in the host fields of remap rules

[ https://issues.apache.org/jira/browse/TS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790878#action_12790878 ] Manjesh Nilange commented on TS-80: --- I feel the ideal place for documentation would be in the

[jira] Created: (TS-87) Performance improvement: Avoid linear search in remap code

Performance improvement: Avoid linear search in remap code -- Key: TS-87 URL: https://issues.apache.org/jira/browse/TS-87 Project: Traffic Server Issue Type: Improvement Compo

[jira] Commented: (TS-80) Support regular expressions in the host fields of remap rules

[ https://issues.apache.org/jira/browse/TS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790869#action_12790869 ] Manjesh Nilange commented on TS-80: --- Leif, you are right. The pcre.h check result is not being

Re: cache partition size patch commit vote request

I suppose the question is whether the remap+Y! changes are merged immediately into the the branch (cutting 2.0) or lazily (wait for 2.0). As long as the changes are relatively isolated the lazy option is easier, or if they come as a package rather than trickle in. Do you know how much of the Y!

Re: cache partition size patch commit vote request

On 12/15/2009 09:48 AM, John Plevyak wrote: Why not cut the 2.0 branch now? We're still waiting to land changes that were made in the Y! internal tree after we moved the source to ASF. We need those into the 2.0 branch, I'm pretty sure. We're also still discussing the changes for the "r

[jira] Created: (TS-86) HTTP cache miss latency huge

HTTP cache miss latency huge Key: TS-86 URL: https://issues.apache.org/jira/browse/TS-86 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: John Plevyak Single clie

Re: cache partition size patch commit vote request

Why not cut the 2.0 branch now? The existing codebase has some serious issues in the event scheduling system (for example large cache miss latencies, an issue I am submitting) along with performance problems handling medium size objects (more than 100k) in addition to the limits handing large ob

Re: cache partition size patch commit vote request

Sorry I'm late to this vote since I've been reviewing and testing out this patch. Preliminary testing indicates good stability with marked improvement in performance. +1 to commit and have in 2.0 release provided the cache has proper regression tests. The code base sorely needs to be updated fo

Re: cache partition size patch commit vote request

On 12/09/2009 05:15 PM, John Plevyak wrote: I would like to ask for a vote on whether or not to commit the cache partition size patch (+1, -1, 0). I think we're gonna have to "call" this vote, and with only 2 +1 and one -1, we need to postpone this checkin until the 2.0 "branch" is cut (and