A
@baris said in test message with link out to another nodebb:
> Those are likely CORS issues, this is from the network tab of chrome when trying to load images from ideologycentral.
The weird thing is, both use the same vhost definition of the NodeBB sites. They are just set to use different ports.
Should be open now in the nginx vhost config.
Added
if ($request_method = OPTIONS ) {
add_header 'Access-Control-Allow-Origin' '*';
add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS, HEAD';
add_header 'Access-Control-Allow-Headers' 'Authorization, Origin, X-Requested-With, Content-Type, Accept';
return 200;
}
if ($request_method ~* '(GET|POST)') {
add_header 'Access-Control-Allow-Origin' '*';
}
Let's see.
Yeah, there are some issues. But even XF has issues with unfurling at times.
Let's see about now. Had a CF rule to have both those images not be cached in CF, which should send it direct to the server. Seems that a 403 is being returned.
Now will do one to my astrophotography site (XF) that I know works.
What is weird is that the first one is on the same server as the second one, and the OG image is available.
https://ideologycentral.com/assets/uploads/system/og-image.jpg
As is the favicon.
https://ideologycentral.com/assets/uploads/system/favicon.ico
It may be something in my vhost definition I need to look at or possible CF cache.
