S3 CDN URL ignored when uploading into posts

[DanielMarquard]

All of our traffic goes through CloudFront, and static content is fetched by CloudFront from one of several S3 buckets.

With uploads being sent to S3, Discourse embeds the content with a generic bucket URL despite our having s3 cdn url set. Once submitted, posts appear to use the correct URL set in s3 cdn url, although this may also be because we have DISCOURSE_CDN_URL set as well (both are set to the same URL).

The post preview window references the standard S3 URL seen in the unbaked post, though. This is a problem because we use a private ACL on files uploaded to our Discourse uploads bucket, as content on this bucket should never be accessed outside of CloudFront. The result is a broken image in the preview window.

[timkelty]

Disappointing this has been reported for so many years with no fix.

@DanielMarquard Did you ever figure out a workaround, or were you forced to make your s3 ACL public?

[Stephen]

I’m not sure it’s fair to suggest this is broken, as much as the more complicated implementation isn’t fully supported.

S3 uploads as documented work and behave correctly.

[timkelty]

@Stephen Certainly up for interpretation…

To me it seems “broken” that it uses the CDN url in one instance and not the other, and it forces an S3 configuration that AWS actually recommends against (public ACL for an s3 bucket).

I’m new to the Discourse project in general, but can certainly work on a PR.

[riking (Kane York)]

This may be worth fixing now - AWS is getting more serious about informing people of public read ACLs.

[sam (Sam Saffron)]

Given our current implementation no longer has an IMG tag eg:

![image|690x298,50%](upload://eGAOR4Xy4aRM2lwPIuTokBf60jS.png)

It should be quite easy to apply a CDN to the above and it saves traffic.

@vinothkannans can you fix this up so preview uses the CDN url

Instead of preview showing:

<img src="//assets-meta-cdck-prod-meta.s3.dualstack.us-west-1.amazonaws.com/original/3X/6/6/66ef078b3ef9da9aa1b3356cb21fe22a0d25eaf0.png" alt="image" class="resizable" width="345" height="149">

We should show the CDN URL which is this:

<img src="https://d11a6trkgmumsb.cloudfront.net/original/3X/6/6/66ef078b3ef9da9aa1b3356cb21fe22a0d25eaf0.png" alt="image" class="resizable" width="345" height="149">

[vinothkannans (Vinoth Kannan)]

Now it’s fixed as per the below commit

FIX: use upload's cdn url in composer preview if available.

[vinothkannans (Vinoth Kannan) A fermé ce sujet ()]

This topic was automatically closed after 32 hours. New replies are no longer allowed.

[RGJ (Richard - Communiteq)]

Suite à la discussion sur L’URL CDN S3 est ignorée lors du téléchargement dans les publications :

Il semble que ce problème ait régressé ; je peux le reproduire ici sur meta.

[codinghorror (Jeff Atwood)]

Peut-on vérifier cela @vinothkannans ou @falco ?

[vinothkannans (Vinoth Kannan)]

Conformément au récent changement, nous récupérons désormais l’URL du fichier téléchargé directement à partir de la requête de téléchargement initiale. Auparavant, nous la recevions via le point de terminaison /uploads/lookup-urls.json. Ce commit devrait résoudre le problème.

FIX: return cdn url for uploads if available.

[Falco]

Il semble que cette correction ne prenne pas en charge les emojis personnalisés dans l’aperçu, par exemple .

[applebee1558 (Alex Liu)]

Cela concerne également les pièces jointes manquantes, telles que les exports de données ou tout autre fichier joint. Ceux-ci proviennent toujours de S3.

[nbianca (Bianca)]

Je peux régler ça !

FIX: Use CDN for custom emojis (#11401)