> First, thanks for the redirect_to patch. I started with that originally.
> Again because this is a common use case, I figured we need to address it in
> the framework, and it looked to me like the low hanging fruit is submitting
> a documentation patch. Documenting this means teaching people that for
> create actions they can't use simple redirect_to, but need to use
> redirect_to in a way that doesn't redirect the original request to the new
> resource, by following this pattern.
As was mentioned by others, you should really be sending 201, so I'm
not even sure this is an issue that merits changing the documentation.
I realise browsers don't support 201 but that's why we have
respond_to
respond_to do |format|
format.xml { head :created...}
format.html { redirect_to wherever... }
end
--
Cheers
Koz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" 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-core?hl=en
-~----------~----~----~----~------~----~------~--~---
