Jump to content
Sign in to follow this  

Ad Blocked by CORS Policy (Console Error)

Recommended Posts


I have version 4.1.4 of Revive running on a site.  I'm seeing an issue when there is a question mark at the end of the URL of a page (for example:  www.example.com? instead of www.example.com) - in such a case, the ad doesn't display for the user.  I took a look and there are a couple of browser console errors:

First console error:

Access to XMLHttpRequest at 'https://subdomain.example.com/adserver/www/delivery/asyncspc.php?zones=1&prefix=revive-0-&loc=https%3A%2F%2Fwww.example.com%2Ffolder%2Ffolder%2Findex.html%3F' from origin 'https://www.example.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Second console error:

https://subdomain.example.com/adserver/www/delivery/asyncspc.php?zones=1&prefix=revive-0-&loc=https%3A%2F%2Fsubdomain2.example.com%2Ffolder%2Ffolder%2Fresults.aspx%3F&referer=https%3A%2F%2Fwww.example.com%2Ffolder%2Ffolder%2Findex.html%3Ftest 403 (Forbidden)

As you can see above, the second error references the file at https://subdomain.example.com/adserver/www/delivery/asyncjs.php

I have Revive running on a subdomain on the site, in a folder...so I used the sample URLs above to demonstrate that (being installed in this example in a folder named adserver in a subdomain named subdomain)


Does anyone know if these errors are a result of a Revive bug or something on my end?

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this