NodeBB-ActivityPub Bridge Test Instance

astro-what@community.nodebb.org

I am wondeirng if it may be because it is behind cloudflare.

accept-ranges: bytes
access-control-allow-origin: *
cache-control: public, max-age=5184000
cf-cache-status: MISS
cf-ray: 902a5f02d1112e6f-DFW
connection: keep-alive
content-length: 23506
content-security-policy: frame-ancestors 'self'
content-type: image/jpeg
cross-origin-opener-policy: same-origin
cross-origin-resource-policy: same-origin
date: Thu, 16 Jan 2025 01:35:50 GMT
etag: W/"5bd2-1945f4d107a"
last-modified: Mon, 13 Jan 2025 10:54:33 GMT
origin-agent-cluster: ?1
referrer-policy: strict-origin-when-cross-origin
server: cloudflare
strict-transport-security: max-age=15552000; includeSubDomains
x-content-type-options: nosniff
x-dns-prefetch-control: off
x-download-options: noopen
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: none
x-powered-by: NodeBB
x-xss-protection: 0

astro-what@community.nodebb.org

@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.

astro-what@community.nodebb.org

Should be open now in the nginx vhost config.

Let's see.

Just a moment...

(ideologycentral.com)

astro-what@community.nodebb.org

Yeah, there are some issues. But even XF has issues with unfurling at times.

astro-what@community.nodebb.org

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.