Jump to content

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?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...