ansaurus

Question

Resolving URI character encoding issues in Rails

Answer 1

A:

This works for me: <%= u name -%>

I use this technique everytime i have to pass on auth token around in my views: <%= u form_authenticity_token %>

Since the above is for views, if you want ruby specific:

require 'uri'
foo = "http://google.com?query=hello"

bad = URI.escape(foo)
good = URI.escape(foo, Regexp.new("[^#{URI::PATTERN::UNRESERVED}]"))

bad_uri = "http://mysite.com?service=#{bad}&amp;bar=blah"
good_uri = "http://mysite.com?service=#{good}&amp;bar=blah"

puts bad_uri
# outputs "http://mysite.com?service=http://google.com?query=hello&amp;bar=blah"

puts good_uri
# outputs "http://mysite.com?service=http%3A%2F%2Fgoogle.com%3Fquery%3Dhello&amp;bar=blah"

Hope this helps.

Shripad K 2010-08-19 04:55:04

Thanks. If this is the solution, however, I need to do it in javascript.The name comes from a jsonp api call, and then is appended to the url.My solution for now was to switch the application to use Ruby 1.8 instead of 1.9.

Gdeglin 2010-08-19 20:45:43

Even if it comes from a jsonp api call i am guessing you are receiving it in the controller's action as `params[:name]`, `params[:recepient_id]` right? Why not just do `URI.escape(params[:name], Regexp.new("[^#{URI::PATTERN::UNRESERVED}]"))`? I see from the log output that you are receiving the parameters.. Just escape it before storing/manipulating the data. If you could provide a skinny version of your controller's action it would be more easier to provide a solution.

Shripad K 2010-08-20 02:28:58

It's a jsonp api call that's all done client side. The data is then sent to a rails controller. It fails inside of Rack before it even hits the controller action.

Gdeglin 2010-08-27 22:11:48

ansaurus

tags:

views:

answers:

Resolving URI character encoding issues in Rails

related questions