Marnen Laibow-Koser wrote in post #972876: > James Byrne wrote in post #972875: >> I am experimenting with a combined form. I wish to force the HTTP verb >> for this form to PUT. However, it always uses POST when submitted and I >> cannot determine why. > > Because that's the way Rails works. Many browsers don't support PUT > forms, so Rails leaves the method as POST and adds a hidden field to > fake what the method "really" is. Rails does the processing of that > hidden field transparently, so that a POST with method "_put" will > appear to the framework exactly like a real PUT. >
Then does that mean one must always provide a route for the new method, even if it makes no sense to do so within a given context? -- 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.
