You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am unable to access the JSON data from my api as part of 'iron-form-response'. I am sending login data to an api on a local development server (running Django w/ django-rest-framework to handle the api). Chrome DevTools show the following response, which is the correct JSON data that I want to work with (I plan to store the access token as a cookie).
The console.log statements should be printing out the request and response information in the event's 'detail' property. While this works for the request...
I am not sure why there is an iron-request object instead of formatted JSON, or how I can go about accessing the response. Any help with this would be greatly appreciated.
--Matt
The text was updated successfully, but these errors were encountered:
Hi,
I am unable to access the JSON data from my api as part of 'iron-form-response'. I am sending login data to an api on a local development server (running Django w/ django-rest-framework to handle the api). Chrome DevTools show the following response, which is the correct JSON data that I want to work with (I plan to store the access token as a cookie).
The headers are as follows (the request URL is my local IP, with the Django development server on port 80):
As you can see, the content-type is set as 'application/json', and the response seems to be perfectly formatted JSON.
My javascript is running the following code:
The console.log statements should be printing out the request and response information in the event's 'detail' property. While this works for the request...
... it does not work as well for the response:
I am not sure why there is an iron-request object instead of formatted JSON, or how I can go about accessing the response. Any help with this would be greatly appreciated.
--Matt
The text was updated successfully, but these errors were encountered: