Sorry for the delay in responding, I was doing training all last week and didn't have time to catch up. Yes, based on the comments this sounds reasonable and I am on board :) I think it should be a goal for items in Asterisk 13 and existing ARI applications to be case-sensitive, lowercase in the TECH field wherever possible. Significant work in Asterisk 12 for this does seem a bit silly as it is a development release. Leif. -----Original Message----- From: Scott Griepentrog <sgriepentrog@xxxxxxxxxx> Reply-to: Asterisk Application Development discussion <asterisk-app-dev@xxxxxxxxxxxxxxxx> To: Asterisk Application Development discussion <asterisk-app-dev@xxxxxxxxxxxxxxxx> Subject: Re: Standardization of Case for ARI URIs Date: Thu, 23 Jan 2014 10:41:34 -0600 Distilling all comments down, I now have this plan which will be implemented unless there is significant disagreement: PREFIX: case sensitive, lower case required PATH: case sensitive, lower case required TECH: case INsensitive (accept SIP & sip), current CAPS will be allowed to continue but recommendation is to lower case all TECH names RESOURCE: case sensitive, must match actual configured value. ID: case sensitive, must match actual identifier OPERATION: case sensitive, lower case required -- Leif Madsen Lead UC Systems Engineer c: +1-613-800-7610 http://thinkingphones.com _______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
