Comments on: RESTful Web apps with Django, Piston and Ext JS

By: Ryan Allen

Ryan Allen — Sat, 04 Sep 2010 00:06:29 +0000

Well, I’m still getting the 400 BAD REQUEST on POSTs.

I’m running Piston 0.2.2 and that patch doesn’t seem to apply to this version.

My request headers from the POST do contain: application/json; charset=UTF-8 (according to firefox 3.6.7/firebug).

I wish I knew what what happening here. I’m somewhat committed to Piston!

By: Orges

Orges — Wed, 18 Aug 2010 15:47:01 +0000

In api/handlers.py one can add to the TaskHandler the following missing crud methods:

def delete(self, request, id):
if not self.has_model():
return rc.NOT_IMPLEMENTED
try:
inst = self.model.objects.get(id=id)
inst.delete()
return rc.DELETED
except self.model.MultipleObjectsReturned:
return rc.DUPLICATE_ENTRY
except self.model.DoesNotExist:
return rc.NOT_HERE

def read(self, request, id):
if not self.has_model():
return rc.NOT_IMPLEMENTED
try:
inst = self.model.objects.get(id=id)
return inst
except self.model.MultipleObjectsReturned:
return rc.DUPLICATE_ENTRY
except self.model.DoesNotExist:
return rc.NOT_HERE

Then one can test it with curl:
delete the task with id=1:
curl -i -H “Accept: application/json” -X DELETE ‘http://localhost:8000/api/tasks/1′

read the task with id=2:
curl -i -H “Accept: application/json” -X GET ‘http://localhost:8000/api/tasks/2′

Hope this helps.

By: Sourcefabric's Dev Blog › Django Software Stack

Sourcefabric's Dev Blog › Django Software Stack — Tue, 06 Jul 2010 14:48:18 +0000

[...] Piston – It’s not magic though, you still need some coding for each model to hook it in: Overview and Tutorial [...]

By: Gerrit Kitts

Gerrit Kitts — Mon, 24 May 2010 01:59:38 +0000

The reason for the 400 errors is that ExtJS is appending a charset onto the Content-Type field, which causes piston to not interpret the Content-Type correcly. There is an open issue for it at http://bitbucket.org/jespern/django-piston/issue/121/content-type-is-not-being-split-against. I was able to get the example working after I applied the patch and did an easy_install.

By: yml

yml — Sat, 01 May 2010 00:38:45 +0000

Hello,
In most of the case that come to my mind I want to restrict the POST, DELETE to authenticated users. Authenticated user in the django sense (@login_required). I would be really interested to hear from you how you enforce this restriction.
Thanks for sharing your experience with django-piston and Ext JS.
Regards,
–yml

By: mdorn

mdorn — Tue, 23 Mar 2010 23:39:40 +0000

Sorry I haven’t had time to look into this — if anyone else has an idea, feel free to post here. Otherwise, hopefully in a couple of weeks I’ll get a chance to take a look.

By: Jars

Jars — Tue, 16 Mar 2010 14:39:42 +0000

I’ve de same problem. Any idea?

By: Chris Hughes

Chris Hughes — Wed, 03 Feb 2010 22:07:06 +0000

I haven’t been able to get this demo to work with ExtJS 3.1. I get 400 BAD REQUEST error anytime I try a POST or PUT request. I was having the same problem with my own code, which is why I installed your demo in the first place. I can get all CRUD methods to work with cUrl technique, and with basic web form requests, but it stops working when I wire up ExtJS grid.

Any ideas? Thanks for any help you can offer.

–ch

By: JAVH

JAVH — Sun, 27 Dec 2009 18:47:27 +0000

Nice tutorial. Thanks a lot!

By: uberVU - social comments

uberVU - social comments — Wed, 23 Dec 2009 13:24:43 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by pnendick: “RESTful Web apps with Django, Piston and Ext JS” http://bit.ly/8mJ5Dw @aquamatt @garethr – any experience with piston? http://bit.ly/4n7oFP...