On Nov 4, 2008, at 9:28 AM, gummybears wrote:
> > Hi, > > I discovered that my webhoster denies HTTP delete's. They suggest I > can do the same via HTTP get's. > As I explained to them I am using their Rails framework via REST and > CRUD, it seems either they don't > know what they are doing or I have to do some serious thinking. > > As I am developing an web application where users can create/edit/ > delete records in a database table, > I thought by using the REST method, I was following RoR guidelines. > > My question is this, are they correct in saying I can use get's > instead of delete's ? If your users are interacting with your site via a web browser then all the requests will be either GET or POST and Rails sneaks in a hidden parameter to set the actual verb (ie. the DELETE you want). If it's a RESTful client that really speaks REST then you're gonna be in trouble. That's my understanding anyway. > P.S Their comment was, DELETE's are very old, you can do the same with > GET's, but the HTTP return > code is different. They only allow the following requests GET POST > OPTIONS PROPFIND > > TIA > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
