I am assuming the same process holds true for the NGINX sever type? Thanks Luceos. I believe this is why I was getting the cros policy errors.
I had this code snippet (incorrectly) at the top of my .HTACCESS file (this code redirects url's to "https" instead of "http"):
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.mywebsite.com/forum$1 [R,L]
And in second-place, I had this code (which ought to have stopped the cros policy errors):
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin "*"
</IfModule>
However this order would randomly generate cros policy errors. Sure... refreshing the page would fix it but it didn't look great with my members.
So I placed Header set Access-Control-Allow-Origin in first place and we'll see how things go. ðŸ¤