I’d also like to add my feedback, since you asked :)

In reference to #3, 303 See Other, I feel that altering the behaviour of redirect_to could be a little murky as you are changing something that is very well know. No Rails developer running your code and examining the output would have any idea why they are seeing a 303 status and not a 301. Even worse, because the redirect_to method is so ubiquitous would they even suspect that it wouldn’t output what it always outputs?

Changing something which is well understood is never a good idea IMHO. I would rather see different flavors of redirect_to like see_other() or redirect_to_other() which make it obvious to the reader that what is being done is not redirect_to but something else, similar but different.

Rather than redirect_to(…, :status => :see_other) which sends an empty response I prefer to use:

def redirect_to_other(location)
render(:inline => “……”, :layout => false, :status => :see_other, :location => location)
end

or similar.

This implementation more closely satisfies the spec which states a 303 SHOULD include a hypertext note with a link to the new location in the response body. Both work, it’s optional, but what the hell. If you’re going to do it anyway why not.

I’ve bunched my multi-flavored redirect_to_…() helpers as a module and include it in ApplicationController:

redirect_permanently_to(…) # => 301
redirect_to_other(…) # => 303
redirect_temporarily_to(…) # => 307

and use the stock redirect_to method for 302 redirects as written. This gets rid of the :status => ### ugliness too in the same way I use named_scope in my models.

Cheers

{ item: { … }, _method: ‘delete’ }

blweiner, I originally wanted one rendering, 303 works for both browser and programs, but perhaps it’s best to separate 201 (programmable) and 303 (browser).

Neville, Ajax.Request accepts the option contentType, just set this to ‘application/json’. But you do need to create a JSON-encoded string, which unfortunately prototype.js doesn’t do for you.

I’m also investigating sending JSON from the browser to my rails app, so you posting is very relevant to me. In your examples, you are using ‘curl’ to contruct the request which works just fine. However, I’m struggling to get prototype.js Ajax.request() to tell Rails that I’m sending application/json so that Rails automagically parses the incoming JSON into params as a ruby hash.

I wonder if you might have a simple Prototype example handy which successfully sends JSON to Rails?

TIA

Neville

Great work on everything you’ve done related to Rails. I’m busy incorporating your work with conditional GET into my app.

Using a container like this has the added benefit of leaving room for adding more information into the json response/request such as errors.