Re: TLS Session Ticket Key Format

On Thu, Aug 21, 2014 at 4:37 PM, James Peach wrote: > On Aug 21, 2014, at 3:56 PM, Bill Zeng wrote: > > > Hi all, > > > > I am new to ATS and my understanding of ATS is limited. I am working on a > > project to enable session resumption using session tickets. Session > tickets > > are encrypted

Re: header-rewrite change

Anybody got $0.02? :-) - Manjesh On Wed, Aug 20, 2014 at 2:13 PM, Manjesh Nilange wrote: > Hi all, > > We have a feature to implement and are wondering if header-rewrite is the > right home for this feature. In a nutshell, when using ATS as a reverse > proxy, we want to re

header-rewrite change

Hi all, We have a feature to implement and are wondering if header-rewrite is the right home for this feature. In a nutshell, when using ATS as a reverse proxy, we want to redirect all http requests with a certain cookie to their https counterparts but not using remap.config. The remap.config cons

RE: C++ wrapper for some API sections

o:mt...@apache.org] > Sent: Thursday, July 22, 2010 3:45 AM > To: dev@trafficserver.apache.org > Subject: Re: C++ wrapper for some API sections > > On 07/22/2010 12:09 AM, Manjesh Nilange wrote: > > The attachments are missing (even though my sent folder email says the > >

RE: C++ wrapper for some API sections

ransaction(INKHttpTxn txnp) : _txnp(txnp) { }; bool getClientReq(HttpRequest &req) { req.clear(); return (INKHttpTxnClientReqGet(_txnp, &req._buf, &req._loc) == 1); } bool getServerResp(HttpResponse &resp) { resp.clear(); return (INKHttpTxnServerRespGet(_tx

C++ wrapper for some API sections

Hi all, I started working on a C++ wrapper for some of the API functions to make some of the data structures easier to use. What I did was basically wrap the pointers and types so that they can be automatically released/destroyed. I abandoned working on this as I have other things on my place. How

[jira] Resolved: (TS-262) Trie code crashes when negative value characters are present in the path

[ https://issues.apache.org/jira/browse/TS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange resolved TS-262. Resolution: Fixed > Trie code crashes when negative value characters are present in the p

RE: [VOTE] Graduate Apache Traffics Server as TLP

> [X] +1 to recommend Apache Traffic Server graduation > [ ] 0 don't care > [ ] -1 no, don't recommend yet, (because...) - Manjesh

[jira] Commented: (TS-253) HTTP Header Host ptr field not set

[ https://issues.apache.org/jira/browse/TS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848929#action_12848929 ] Manjesh Nilange commented on TS-253: We did have a problem when we added a new membe

[jira] Commented: (TS-253) HTTP Header Host ptr field not set

[ https://issues.apache.org/jira/browse/TS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848430#action_12848430 ] Manjesh Nilange commented on TS-253: It seemed to work fine for me: (gdb) wher

[jira] Commented: (TS-253) HTTP Header Host ptr field not set

[ https://issues.apache.org/jira/browse/TS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848297#action_12848297 ] Manjesh Nilange commented on TS-253: John, I'm generally new to TS code and spe

[jira] Created: (TS-262) Trie code crashes when negative value characters are present in the path

Type: Bug Components: Core Reporter: Manjesh Nilange Assignee: Manjesh Nilange Fix For: 2.0.0a The trie code expects all the characters in the path to be legal ASCII values (<128). However to make it secure for now (to discount rogue characters caus

[jira] Resolved: (TS-261) Use correct logger type and debug tags in mapping lookup

[ https://issues.apache.org/jira/browse/TS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange resolved TS-261. Resolution: Fixed > Use correct logger type and debug tags in mapping loo

[jira] Updated: (TS-261) Use correct logger type and debug tags in mapping lookup

[ https://issues.apache.org/jira/browse/TS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-261: --- Fix Version/s: 2.1.0 > Use correct logger type and debug tags in mapping loo

[jira] Created: (TS-261) Use correct logger type and debug tags in mapping lookup

Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Trivial The mapping lookup function is causing error messages in the log in what appears to be normal functioning of TS. -- This message is automatically

[jira] Updated: (TS-237) catch-all remap rule ("map / ....") stopped working after lookup optimizations

[ https://issues.apache.org/jira/browse/TS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-237: --- Attachment: catchall-remap.patch Proposed change. > catch-all remap rule ("map / &q

[jira] Assigned: (TS-237) catch-all remap rule ("map / ....") stopped working after lookup optimizations

[ https://issues.apache.org/jira/browse/TS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange reassigned TS-237: -- Assignee: Leif Hedstrom (was: Manjesh Nilange) Leif, review please. > catch-all remap r

[jira] Created: (TS-237) catch-all remap rule ("map / ....") stopped working after lookup optimizations

fic Server Issue Type: Bug Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Fix For: 2.0.0 A "catch-all" remap rule like: map / http://example.com has stopp

[jira] Updated: (TS-236) url copy function should duplicate host fields

[ https://issues.apache.org/jira/browse/TS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-236: --- Affects Version/s: 2.0.0a Fix Version/s: (was: 2.0.0a) 2.0.0 >

[jira] Assigned: (TS-236) url copy function should duplicate host fields

[ https://issues.apache.org/jira/browse/TS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange reassigned TS-236: -- Assignee: Leif Hedstrom (was: Manjesh Nilange) Leif, please review. > url copy function sho

[jira] Updated: (TS-236) url copy function should duplicate host fields

[ https://issues.apache.org/jira/browse/TS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-236: --- Attachment: host_copy.patch Patch with proposed change. > url copy function should duplicate h

[jira] Created: (TS-236) url copy function should duplicate host fields

Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Fix For: 2.0.0a The change for https://issues.apache.org/jira/browse/TS-185 makes sure that url_host_set() doesn't free/reallocate new memory on every call, but optimally grows the buffer. Th

[jira] Updated: (TS-158) cache should not hold parititon lock over callbacks/review locking

[ https://issues.apache.org/jira/browse/TS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-158: --- Attachment: compiler-errors.patch The typecasting that fixes these errors. > cache should not h

[jira] Assigned: (TS-194) TS is not using case-normalized host string to lookup remap rules and regex remap rules are not being case normalized

[ https://issues.apache.org/jira/browse/TS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange reassigned TS-194: -- Assignee: Leif Hedstrom (was: Manjesh Nilange) Leif, please review. > TS is not using c

[jira] Updated: (TS-194) TS is not using case-normalized host string to lookup remap rules and regex remap rules are not being case normalized

[ https://issues.apache.org/jira/browse/TS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-194: --- Attachment: case-normalization.patch 1) Moved case normalization code from _tableLookup to

[jira] Created: (TS-194) TS is not using case-normalized host string to lookup remap rules and regex remap rules are not being case normalized

://issues.apache.org/jira/browse/TS-194 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Fix For: 2.0.0a -- This message is automatically

[jira] Updated: (TS-106) TS should raise warning for duplicate remap rules

[ https://issues.apache.org/jira/browse/TS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-106: --- Attachment: duplicate-remap-rule.patch Patch created with "svn diff" against latest trunk fil

[jira] Assigned: (TS-106) TS should raise warning for duplicate remap rules

[ https://issues.apache.org/jira/browse/TS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange reassigned TS-106: -- Assignee: Leif Hedstrom (was: Manjesh Nilange) Leif, please review. > TS should raise warn

[jira] Updated: (TS-106) TS should raise warning for duplicate remap rules

[ https://issues.apache.org/jira/browse/TS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-106: --- Attachment: UrlRewrite.h.patch UrlRewrite.cc.patch > TS should raise warning

[jira] Updated: (TS-184) Host header/cache lookup entry doesn't match remap.config perfectly

[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-184: --- Attachment: port-80.patch Patch on top of TS-87 changes. > Host header/cache lookup entry does

[jira] Assigned: (TS-185) url_host_set() is free-ing and allocating memory at every call which is triggering a crash in the heap code

[ https://issues.apache.org/jira/browse/TS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange reassigned TS-185: -- Assignee: Leif Hedstrom (was: Manjesh Nilange) Leif, please review. > url_host_set() is f

[jira] Updated: (TS-185) url_host_set() is free-ing and allocating memory at every call which is triggering a crash in the heap code

[ https://issues.apache.org/jira/browse/TS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-185: --- Attachment: url_host_set.patch This patch introduces a new member variable - m_capacity_host. This

[jira] Created: (TS-185) url_host_set() is free-ing and allocating memory at every call which is triggering a crash in the heap code

/jira/browse/TS-185 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Fix For: 2.0.0a url_host_set() is calling this function every time: const

[jira] Assigned: (TS-184) Host header/cache lookup entry doesn't match remap.config perfectly

[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange reassigned TS-184: -- Assignee: Leif Hedstrom (was: Manjesh Nilange) Leif, please review. Thanks! > Host header/ca

[jira] Created: (TS-184) Host header/cache lookup entry doesn't match remap.config perfectly

: Bug Components: Core Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Fix For: 2.0.0a Attachments: port-80.patch If I had this in my remap.config map http://a.com http://b.com:80 The Host header and the cach

[jira] Updated: (TS-184) Host header/cache lookup entry doesn't match remap.config perfectly

[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-184: --- Attachment: port-80.patch Patch to set the port to match exactly what's specified in remap.c

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

[ https://issues.apache.org/jira/browse/TS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834102#action_12834102 ] Manjesh Nilange commented on TS-87: --- Leif, I tested the patch with a similar remap.config

[jira] Assigned: (TS-175) TS always sends port string 80 in Host header to OS irrespective of remap.config

[ https://issues.apache.org/jira/browse/TS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange reassigned TS-175: -- Assignee: Leif Hedstrom (was: Manjesh Nilange) Leif, can you please review the patch? Thanks

[jira] Updated: (TS-175) TS always sends port string 80 in Host header to OS irrespective of remap.config

[ https://issues.apache.org/jira/browse/TS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-175: --- Attachment: explicit-port-80.patch This patch gets the raw port from the mapping and sets it only if it

[jira] Created: (TS-175) TS always sends port string 80 in Host header to OS irrespective of remap.config

Issue Type: Bug Components: Core Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Attachments: explicit-port-80.patch If I have this in my remap.config: map http://ts.com http://real.com TS always sends the Host

[jira] Resolved: (TS-134) Having same host field in a map and regex_map rule causes crash

[ https://issues.apache.org/jira/browse/TS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange resolved TS-134. Resolution: Invalid I'm closing this ticket as invalid. I noticed this behavior only in Yah

[jira] Created: (TS-134) Having same host field in a map and regex_map rule causes crash

Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Having rules like map http://a.com http://b.com regex_map http://a.com http://b.com and then sending a request for http://a.com causes server to

[jira] Commented: (TS-106) TS should raise warning for duplicate remap rules

[ https://issues.apache.org/jira/browse/TS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828397#action_12828397 ] Manjesh Nilange commented on TS-106: Leif, I'm not sure if you reassigned this

[jira] Created: (TS-110) Improve regex remap to allow substitutions in path field

Components: Core Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Currently, regex support covers only the host field of the remap rules. It'd be nice to extend this to allow substitutions into the path field as well. This will allow rules

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

[ https://issues.apache.org/jira/browse/TS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799983#action_12799983 ] Manjesh Nilange commented on TS-87: --- I should've added this in the patch descrip

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

[ https://issues.apache.org/jira/browse/TS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-87: -- Attachment: trie.patch Implementation of proposed change > Performance improvement: Avoid linear search

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

[ https://issues.apache.org/jira/browse/TS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799980#action_12799980 ] Manjesh Nilange commented on TS-87: --- Proposed change: Design: We create a trie for all

[jira] Updated: (TS-105) TS does not process must/proxy revalidate correctly

[ https://issues.apache.org/jira/browse/TS-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjesh Nilange updated TS-105: --- Attachment: mp-reval.patch HttpTransact.cc patch with fix. > TS does not process must/proxy revalid

[jira] Created: (TS-106) TS should raise warning for duplicate remap rules

Nilange Assignee: Manjesh Nilange Priority: Minor Currently, TS silently ignores (newer) duplicate rule. It should raise a warning to alert user of situation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue

[jira] Created: (TS-105) TS does not process must/proxy revalidate correctly

Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Currently, even though TS stores items with must/proxy revalidate in the cache, they are never served out, when in fact the items can be stored. Correct handling as per http://www.w3.org/Protocols

[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=12792739#action_12792739 ] Manjesh Nilange commented on TS-80: --- I've forwarded some text describing this f

[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

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

Components: Core Reporter: Manjesh Nilange Assignee: Manjesh Nilange Priority: Minor Currently, the remap code stores all the remap rules in a hash table keyed by the host field of the "from URL" of the rule. Entries with the same host field are ch

[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

RE: coding style: to camel or not

> MACROS > ClassNames > memberFunctions > members_variables How about having an 'm_' prefix to distinguish member variables from local variables? I know this is a couple of more characters to type, but I find it nicer to be able to distinguish class member variables easily. The rest of the list lo

RE: coding style

ace ts' also be camel-cased to 'Ts'? - Manjesh From: Leif Hedstrom [mailto:zw...@apache.org] Sent: Wednesday, December 09, 2009 3:26 PM To: Manjesh Nilange Subject: Fwd: coding style Original Message Subject: coding style Date: Wed, 9 Dec 200

[jira] Created: (TS-81) Have one single place to store and lookup remap rules irrespective of type

Type: Improvement Components: Core Affects Versions: 2.0a Reporter: Manjesh Nilange Priority: Minor Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and

[jira] Updated: (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:all-tabpanel ] Manjesh Nilange updated TS-80: -- Attachment: regex-support-final.patch Final version of the patch. Changes: 1) Public methods changed to

[jira] Updated: (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:all-tabpanel ] Manjesh Nilange updated TS-80: -- Attachment: regex-support-coding-style.patch Patch previously attached but with coding style applied

[jira] Updated: (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:all-tabpanel ] Manjesh Nilange updated TS-80: -- Attachment: regex-support.patch This is a proposed implementation of the described feature. The

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

Components: Core Affects Versions: 2.0a Reporter: Manjesh Nilange Priority: Minor Fix For: 2.0a Currently, the remap rules cannot have regular expressions in the host fields. Even though regular expressions are supported by the regex_remap plugin for the

[jira] Commented: (TS-48) Change all regex code to use PCRE

[ https://issues.apache.org/jira/browse/TS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780321#action_12780321 ] Manjesh Nilange commented on TS-48: --- I ran a simple rudimentary performance test where