http://badpopcorn.com/blog/2007/03/30/ruby-uri-percent-encoding/ Solutions for anything... except popcorn. Tue, 25 May 2010 09:36:40 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://badpopcorn.com/blog/2007/03/30/ruby-uri-percent-encoding/comment-page-1/#comment-38872 Matma Rex Thu, 06 May 2010 13:25:27 +0000 http://badpopcorn.com/2007/03/30/ruby-uri-percent-encoding/#comment-38872 It is because URI.escape is supposed to operate on whole URIs (which can contain ampersands and slashes) and CGI.escape on query parts. It is because URI.escape is supposed to operate on whole URIs (which can contain ampersands and slashes) and CGI.escape on query parts.

]]> http://badpopcorn.com/blog/2007/03/30/ruby-uri-percent-encoding/comment-page-1/#comment-38854 book Sat, 16 Jan 2010 19:03:34 +0000 http://badpopcorn.com/2007/03/30/ruby-uri-percent-encoding/#comment-38854 nice post, thanks for sharing. I usually don’t post on Blogs but ya forced me to, great info. nice post, thanks for sharing.
I usually don’t post on Blogs but ya forced me to, great info.

]]> http://badpopcorn.com/blog/2007/03/30/ruby-uri-percent-encoding/comment-page-1/#comment-38847 Scott Fri, 18 Sep 2009 23:44:28 +0000 http://badpopcorn.com/2007/03/30/ruby-uri-percent-encoding/#comment-38847 I ran into this same issue when we were constructing a querystring for use with a web service. One of the data values had an & the middle of it which didn't get encoded with the URI.encode or URI.escape. CGI::escape() did the trick. I ran into this same issue when we were constructing a querystring for use with a web service. One of the data values had an & the middle of it which didn’t get encoded with the URI.encode or URI.escape. CGI::escape() did the trick.

]]> http://badpopcorn.com/blog/2007/03/30/ruby-uri-percent-encoding/comment-page-1/#comment-10100 Phillip Novess Fri, 04 May 2007 04:39:27 +0000 http://badpopcorn.com/2007/03/30/ruby-uri-percent-encoding/#comment-10100 Not only did URI not encode the ampersand but it neglected the /. I noticed this same issue with strings like "3/4" in a url. Not only did URI not encode the ampersand but it neglected the /. I noticed this same issue with strings like “3/4″ in a url.

]]>