Oh boy, this was a crazy one. It wasn't url_for that was behaving differently. url_for on both servers seperates query parameters with & (url_for the helper method; url_for the controller method does not. I did not know this. Kinda confusing and unpredictable--and undocumented).
But okay. I was then passing it through REXML in order to 'escape' it for eventual inclusion in some XML: xml_escaped = REXML::Text.new( generated_url ).to_s The difference between my two servers was ruby version, not Rails version. REXML is included with stock ruby (I didn't realize that either). REXML::Text that comes with ruby 1.8.5 will not 'double escape' & to & . I guess I'd consider that a bug, indeed. It probably should be double escaping something like that, if you pass it in escaped. REXML::Text that comes with ruby 1.8.6, on the other hand, WILL double escape that text passed in escaped. Wooh, what a mess. Jonathan Jonathan Rochkind wrote: > I have two different servers, with two different test rails apps, both > of which claim to be running Rails 2.1.2. > > On one of them, url_for in a view environment generates & in between > query parameters, instead of just &. On the other, it generates just &. > > Huh? I can't figure out why this is one way in one app that claims to be > Rails 2.1.2, and another in another. > > In neither one does url_for called in a controller context (rather than > a helper context) use "&" to separate query parameters, it just uses > "&". > > It's driving me crazy. Anyone have any idea what might be going on? > > Jonathan -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
