Comments on: More URI-Related UDFs http://blog.stevenlevithan.com/archives/more-uri-udfs A JavaScript and regular expression centric blog Tue, 07 Sep 2010 15:50:02 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Matt Brundage http://blog.stevenlevithan.com/archives/more-uri-udfs/comment-page-1#comment-51797 Matt Brundage Wed, 28 Apr 2010 13:55:30 +0000 http://blog.stevenlevithan.com/?p=11#comment-51797 Your solution is applicable in the vast majority of cases. I was trying to account for ampersands in the query string that were already part of an encode -- for instance "<code>ß</code>" But then again, such ampersands would ultimately be interpreted as normal query string delimiters -- if they hadn't already been URL-encoded as "<code>%26</code>". Your solution is applicable in the vast majority of cases. I was trying to account for ampersands in the query string that were already part of an encode — for instance “&szlig;” But then again, such ampersands would ultimately be interpreted as normal query string delimiters — if they hadn’t already been URL-encoded as “%26“.

]]> By: Steven Levithan http://blog.stevenlevithan.com/archives/more-uri-udfs/comment-page-1#comment-51771 Steven Levithan Wed, 28 Apr 2010 07:07:52 +0000 http://blog.stevenlevithan.com/?p=11#comment-51771 Hey Matt! Since CGI.QUERY_STRING is used in non-HTML-rendering contexts, it would be inappropriate for CF to automatically use HTML entities in its value. If you want to use the value in valid HTML, yes, the ampersands need to be replaced with "&", but I'd recommend something along the lines of the more straightforward <code><cfif len(cgi.query_string)><cfset queryHtml = "?" & replace(cgi.query_string, "&", "&", "all") /></cfif></code>. Excluding some ampersands from HTML encoding as is done in your above regex seems incorrect here, unless I'm missing something. Hey Matt!

Since CGI.QUERY_STRING is used in non-HTML-rendering contexts, it would be inappropriate for CF to automatically use HTML entities in its value. If you want to use the value in valid HTML, yes, the ampersands need to be replaced with “&amp;”, but I’d recommend something along the lines of the more straightforward <cfif len(cgi.query_string)><cfset queryHtml = "?" & replace(cgi.query_string, "&", "&amp;", "all") /></cfif>. Excluding some ampersands from HTML encoding as is done in your above regex seems incorrect here, unless I’m missing something.

]]> By: Matt Brundage http://blog.stevenlevithan.com/archives/more-uri-udfs/comment-page-1#comment-51717 Matt Brundage Tue, 27 Apr 2010 16:31:12 +0000 http://blog.stevenlevithan.com/?p=11#comment-51717 Sadly, CGI.QUERY_STRING doesn't escape its ampersands, so we must add them back in: <cfset pageQuery = reReplace("?" & reReplace(CGI.QUERY_STRING, "&(?:(?=\s)|(?!(?:\w{2,7}|##\d{2,5});))", "&", "ALL"), "\?$", "") /> See line 15. Sadly, CGI.QUERY_STRING doesn’t escape its ampersands, so we must add them back in:
<cfset pageQuery = reReplace(“?” & reReplace(CGI.QUERY_STRING, “&(?:(?=\s)|(?!(?:\w{2,7}|##\d{2,5});))”, “&amp;”, “ALL”), “\?$”, “”) />

See line 15.

]]>