Closed rohitvinay closed 7 years ago
Hi Rohit-
Whenever you see a generic 403 error come back from API Gateway mentioning No "Access-Control-Allow-Origin" header present this is due to the fact that API Gateway's built-in error handlers do not currently return the needed CORS headers to display the actual error message directly in a browser, at least when running via localhost emulation. If you run the app directly on your mobile device or without using "ionic serve," you will see the actual error going on, but generally for any 403, it's simply "user is unauthorized." That said, you can gain more insight into these actual issues by looking at the network traffic window in the Chrome developer tools and dig into the details of the failed 403 response request. It will likely show you the real error you're looking for there.
Let us know if you have any more trouble with the project's features. If you haven't pulled it in a while, you may want to pull it now as some major features were added this week.
Thanks,
Justin
I want to list the locations, according to
UserId
similar to bookings, I changed theaddLocation
to thisand
locationsCreate
to thisI get the below error if i try to add new locations
XMLHttpRequest cannot load https://cg7fazfa5q.execute-api.us-east-1.amazonaws.com/development/locations. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8101' is therefore not allowed access. The response had HTTP status code 403.