L'URL CDN deve essere aggiunto a csp script src

Supporto Installazione
1

Ho configurato un sito con ENV in questo modo:


  DISCOURSE_FORCE_HTTPS: true
  DISCOURSE_S3_ACCESS_KEY_ID: 'KEY'
  DISCOURSE_S3_SECRET_ACCESS_KEY: 'SECRET'
  DISCOURSE_BACKUP_LOCATION: 's3'
  DISCOURSE_ENABLE_S3_UPLOADS: true
  DISCOURSE_ENABLE_S3_INVENTORY: false
  DISCOURSE_S3_BACKUP_BUCKET: 'mybucket/backups'
  DISCOURSE_S3_UPLOAD_BUCKET: 'mybucket'
  DISCOURSE_S3_CDN_URL: 'https://mybuckets3.cdn.literatehosting.com'
  DISCOURSE_S3_REGION: 'us-west-1'
  DISCOURSE_BACKUP_WITH_UPLOADS: 'false'
  DISCOURSE_CDN_URL: 'https://mybucket.cdn.literatehosting.com'

Funzionava perfettamente finché non ho aggiunto l’s3 cdn url. Dopo aver aggiunto il CDN S3, il mio browser ha iniziato a rifiutare le richieste al CDN normale (non S3). Ho aggiunto l’URL del CDN a SiteSetting.content_security_policy_script_src= e poi ha funzionato di nuovo. Sembra un bug, vero? Ho semplicemente eseguito un riavvio dopo aver modificato queste variabili ENV, non una rebuild. È necessario eseguire un rake assets:precompile quando si modificano le impostazioni del CDN?

2

Hmm, this should be working fine. The CSP is supposed to whitelist the specific folders on the S3 and pull CDNs that scripts come from.

What CSP was/is Discourse sending with the page? Is this a subfolder install?

1 Mi Piace
3

I think I understand that. Is that CSP in the static assets that a rake assets:precompile makes? (But then why would adding it to the settings fix it.)

I’m afraid that I don’t quite know the canonical way to get the answer to that question.

Not subfolder. A fairly standard install, though traefik is a reverse proxy in front of it.

4

curl -I https://discourse.example.com/ or the Chrome inspector, and get the content of the Content-Security-Policy header.

2 Mi Piace