First, thanks to all for their answers/comments. I think I am out of luck, my ISP is not supporting the DELETE, period. Either I try including the _method=DELETE or perhaps to construct a rewrite rule in .htaccess to get around the problem. Lastly as I was also experiencing other issues with my current ISP (no ssh support, they say it's unsafe, only ftp support) so I was thinking to move to another ISP. Hopefully their web environment is better suited for the things I am trying to accomplish.
BTW I updated my code to use the POST request with the extra parameter _method=DELETE. This works, the right controller is called with the correct params and action. But in the Rails log I am also seeing extra parameters passed on (things like /:controller/:id.html/:id => nil), something to do how Apache/fcgi passes the request to Rails (rewrite rules in .htaccess) On 4 nov, 22:13, Philip Hallstrom <[EMAIL PROTECTED]> wrote: > On Nov 4, 2008, at 11:02 AM, Robert Walker wrote: > > > > >> If it's a RESTful client that really speaks REST then you're gonna be > >> in trouble. > > Why would he be in trouble? What would stop him from sneaking in the > > same parameter into a POST request just like Rails does? > > > Verb & URL: > > POST /resources/1 > > > Parameters: > > _method=DELETE > > > Would that not work? I'm not sure since I haven't tried it. > > Because a real RESTful client would want to say "DELETE /resources/1" > and not mess around with the hacks to trick web browsers into being > able to simulate REST by passing _method. > > But, if all his users are using web browsers he's fine. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
