Now that I've done a bit more testing, I think this is simply a namespace collision. I think that query parameters and form parameters share a namespace (the request), and it's reasonable to have weird or undefined behavior when there is a collision. It seems like Rails behavior is to handle the form params first, putting them in the 'params' hash, then handle the query params. The Hash class' behavior would dictate a 'last in wins' behavior, which is consistent with what I'm seeing.
I found that I don't really have to encode that parameter in the URL, which solves my immediate problem. Thanks! -- 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 -~----------~----~----~----~------~----~------~--~---
