Image preview is broken

[dfateyev]

The image preview on the download page appears to be broken: it points to the image URL which is the HTML-page itself.
Could you suggest how to fix it for a self-hosted installation?

Also, grunt blames a lot of outdated / obsolete components, maybe worth to update them.
Unfortunately, I am not familiar with npm ecosystem and cannot figure it out.

[paolafrancesca]

hello @dfateyev

The image preview on the download page appears to be broken: it points to the image URL which is the HTML-page itself.
Could you suggest how to fix it for a self-hosted installation?

that's not 100% correct. the preview url and the url that serves the original content of the file is the same. if the refer in the http request is empty or it is not the same of the of the one in the current request, the preview page will be shown, otherwise you'll get the original content.
so either your browser is sending a refer that it should not send or maybe you are using a proxy path and there's an issue with the proxy configuration that interferes with the referers match.

please, share the content of the http request and response and the url you talking about in the download page (you can anonymize components but not strip them). also this issue should belong to the main application :)

[dfateyev]

that's not 100% correct. the preview url and the url that serves the original content of the file is the same. if the refer in the http request is empty or it is not the same of the of the one in the current request, the preview page will be shown, otherwise you'll get the original content. so either your browser is sending a refer that it should not send or maybe you are using a proxy path and there's an issue with the proxy configuration that interferes with the referers match.

Thanks for your reply, it made me to investigate the headers deeper.
I use a proxy chain, the request is proxied via CloudFlare — and it turned out CF cached the page URL providing the content from cache, so the image content was the same as the preview page content requested initially.
I probably can tune caching with some CF rules, but cannot figure out the criteria since the both URLs are equal, the preview page request also has Referer HTTP-header set, etc — if you have an idea, please let me know.
Right now, I have solved it switching off all caching with add_header Cache-Control "no-store" always on NGINX upstream.

Although, I believe the module update request (the second part) is still valid, and related to this repo 😸