Access control allow origin header code#

This is quite different than my case in the sense mine is in same domain.Ĭan anyone help me on this with possible solutions ?Ĭross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at $SM$N5MjfOF7Ss%2b4YvM6g38sJLDA8KiTWcgLkNWF%2bhD78DX9sULYtX9%2f4dPFqsx7VsXM2W5e5zBrrISBqpTX56FUJB4TnUMmOHN&TARGET=$SM$https%3a%2f%2fabc%2ee%example%2enet%2fprotected%2fcommon%2fresources%2fusers%2f_meta%2fcurrent. I have also gone through the article These cross domain XMLHttpRequest fails to reach the actual server. The solution is currently working with all the browsers except this case. We are providing SSO to many application and we had no such issues till now. Since here is the origin we need to set this as Access-Control-Allow-Origin in webserver corresponding to domain.īoth are in the same domain i.e.e. Its a case of adding the following to your PHP scripts:

Access control allow origin header code#

Based on firefox documentation (HTTP access control (CORS) - HTTP | MDN ) we have noted that if there are requests to a resource from a different domain, protocol, or port to its own, then Access-Control-Allow-Origin has to be set to the origin. Also - if you happen to be getting a status code of 0 or 1 from a request running through API Gateway, this is probably your issue. 'Īs depicted in error message Access-Control-Allow-Origin header is missing in server response.This issue is very specific to firefox and chrome. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). We received the following error message 'Ĭross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at $SM$N5MjfOF7Ss%2b4YvM6g38sJLDA8KiTWcgLkNWF%2bhD78DX9sULYtX9%2f4dPFqsx7VsXM2W5e5zBrrISBqpTX56FUJB4TnUMmOHN&TARGET=$SM$https%3a%2f%2fabc%2ee%example%2enet%2fprotected%2fcommon%2fresources%2fusers%2f_meta%2fcurrent. Now when we call protected resource, there is a redirection to weblogin but there are no contents (blank page). The application is deployed in domain and weblogin in domain. We have an application which is protected by siteminder.