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
This is very much out of scope as I have forked your nice starter and started building something on top of it; to begin with, a login system.
To keep it short, I have created an endpoint at /api/login which calls a method that returns a user + JSON web token(JWT). This works via cURL, however, it does not appear to work when accessing it through the dev server.
Hi @cbll seems to quite out of scope right now. I hope to have a look into a login form in the near future, maybe I can help you then. Just out of curiosity: With the latest commits, we don´t need the complex CORS configuration any more to develop locally - this is handles through webpack-dev-server proxy feature. Can you give it a try with that config? Cheers!
This is very much out of scope as I have forked your nice starter and started building something on top of it; to begin with, a login system.
To keep it short, I have created an endpoint at /api/login which calls a method that returns a user + JSON web token(JWT). This works via cURL, however, it does not appear to work when accessing it through the dev server.
The problem is described here: https://stackoverflow.com/questions/47508348/axios-post-throws-network-error-cross-origin-request-blocked
Wondering if you have any ideas?
For example, via cURL I do get the correct response:
Request:
Response:
But from the frontend via the dev server.
Request:
Response:
STATUS 403
Response head:
The text was updated successfully, but these errors were encountered: