{"id":5064,"date":"2016-05-12T01:50:38","date_gmt":"2016-05-11T15:50:38","guid":{"rendered":"https:\/\/www.businesslegions.com\/blog\/?p=5064"},"modified":"2016-05-11T19:01:50","modified_gmt":"2016-05-11T09:01:50","slug":"resolving-issue-with-cross-origin-resource-sharing-policy-websites","status":"publish","type":"post","link":"https:\/\/www.businesslegions.com\/blog\/2016\/05\/12\/resolving-issue-with-cross-origin-resource-sharing-policy-websites\/","title":{"rendered":"RESOLVING ISSUE WITH CROSS ORIGIN RESOURCE SHARING POLICY FOR WEBSITES"},"content":{"rendered":"

Another issue that we experienced was displaying content from different domains especially when using HTTP and HTTPS. Here’s an example of the error message:<\/p>\n

Font from origin ‘https:\/\/website’ has been blocked from loading by Cross-Origin Resource Sharing policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘http:\/\/website’ is therefore not allowed access.<\/p>\n

The fix is to add the following statement to either the .htaccess file or if you’re using nginx VPS then add it to the nginx.conf file in \/etc\/nginx\/<\/p>\n

add_header ‘Access-Control-Allow-Origin’ ‘*’;<\/em><\/p>\n

\"resolving<\/a>

resolving issue with cross origin resource sharing policy for websites<\/p><\/div>\n

Once you’ve added it to the nginx.conf file make sure to restart the service by using the command:<\/p>\n

service nginx restart<\/p>\n

Then you can test it by using curl -I http:\/\/website<\/em><\/p>\n

\"resolving<\/a><\/p>\n

If the curl result has Access-Control-Allow-Origin: * then it means the nginx changes worked.<\/p>\n

DO YOU LIKE WHAT YOU'VE READ?<\/div>
Join our subscription list and receive our content right in your mailbox. If you like to receive some Great deals our Freebies then subscribe now!\r\n\r\n

\n
\n\n