I'm running across a really weird error where the fetch API (in a React-Native project) leads to a CSRF error but cURL doesn't lead to the same error. Here's the notable code:
Fetch code:
_signup = () => {
fetch('http://localhost/users/', {
method: 'post',
headers: {
'Accept': 'application/json',
'Content-Type': 'application/json',
},
body: JSON.stringify(this.state)
}).then(response => {
return response.json();
}).then(jsonResponse => {
console.log(jsonResponse);
}).catch (error => {
console.log(error)
})
}
which gives the following response
Object {
"detail": "CSRF Failed: CSRF token missing or incorrect.",
}
and the cURL code is:
curl -X POST -d '{"username":"a", "email":"", "password":"a"}' -H "Content-Type: application/json" http://localhost/users/
where the response is
{"url":"http://localhost/users/13/","username":"a7","email":""}
the relevant Django view is just a viewset:
Django View:
class UserViewSet(viewsets.ModelViewSet):
"""
API endpoint that allows users to be viewed or edited.
"""
queryset = User.objects.all()
serializer_class = UserSerializer.
Is there any reason this should be happening? As far as I know, fetch and curl should be doing the same thing?
