both of them work woth a load of sensible defaults taking the URL from the href or the action and the method from the method attribute. The form automatically serializes the data from the form its attached to to send.
On top of this, the Remote.Form behavior helps serialization by only sending the submit button that you pressed in the request.
> both of them work woth a load of sensible defaults taking the URL from
> the href or the action and the method from the method attribute. The
> form automatically serializes the data from the form its attached to
> to send.
> On top of this, the Remote.Form behavior helps serialization by only
> sending the submit button that you pressed in the request.
Am I wrong or do these behaviors not work with the new rails
protect_from_forgery. Was having trouble with the remote behavior
until I disabled it. Any way to get the two to work together nicely?
On 5 Feb, 16:51, "Dan Webb" <d...@danwebb.net> wrote:
> both of them work woth a load of sensible defaults taking the URL from
> the href or the action and the method from the method attribute. The
> form automatically serializes the data from the form its attached to
> to send.
> On top of this, the Remote.Form behavior helps serialization by only
> sending the submit button that you pressed in the request.
They should do as long as you make sure they serialize the hidden field with the anit forgery token in as well as the other data.
On 2/25/08, donald.pi...@gmail.com <donald.pi...@gmail.com> wrote:
> Am I wrong or do these behaviors not work with the new rails > protect_from_forgery. Was having trouble with the remote behavior > until I disabled it. Any way to get the two to work together nicely?
|
