Reputation: 109
SPA is not working in online hositng
I recently published my SPA to the free account of hostinger.in. In localhost the application works fine. But in online account it not loading views and producing errors in console mentioned bellow.
"XMLHttpRequest cannot load http://error.hostinger.eu/?. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://mdm.890m.com' is therefore not allowed access."
PLese help me to solve the issue!
Upvotes: 1
Views: 351
Answers (1)
Reputation: 36
The relative path in your templateUrls are wrong in app.js Please remove the "mdm" directory from your template urls. So templateUrl: '/mdm/html/fundtype.html' becomes templateUrl: '/html/fundtype.html'
Also the error output is misleading in this case, as your host does a 302 redirect to a 404 page on a different host, causing the CORS error. This is not a CORS problem because your initial request is for the same host.
Upvotes: 2
Related Questions
- Trying to use fetch and pass in mode: no-cors
- Open a URL in a new tab (and not a new window)
- Why does my JavaScript code receive a "No 'Access-Control-Allow-Origin' header is present on the requested resource" error, while Postman does not?
- XMLHttpRequest cannot load XXX No 'Access-Control-Allow-Origin' header
- What does the !! (double exclamation mark) operator do in JavaScript?
- No 'Access-Control-Allow-Origin' header is present on the requested resource—when trying to get data from a REST API
- No 'Access-Control-Allow-Origin' - Node / Apache Port Issue
- Response to preflight request doesn't pass access control check - No 'Access-Control-Allow-Origin' header
- how to add cors in couchDB -- No 'Access-Control-Allow-Origin' header is present on the requested resource
- No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '...' is therefore not allowed access