Is there anyway around cleaning up this URL that it appears to be part of their actual website’s domain. These reports are being sent to a Finance Board who have described the URL as ‘untrustworthy’. Does Webflow have a solution around this or at least a recommendation?
Do we think this will ever be changed?
We have have several different clients on Webflow complaining about this. They don’t want to see files from their website having URLS like: https://assets.website-files.com/63d7a806c35c616efe89445c/644653d047bf1a3ea295907e.pdf
All I can suggest to them is they host the file on their own domain’s hosting and we point to this native URL. Are there any other workarounds?
Good to know. Normally, I’d just have a webserver set up and just set Apache/Nginx to serve files up from a public directory. But DO’s Spaces looks a lot easier to use for someone not familiar with that kind of thing (common in the Webflow community, it seems). So if you’re going “no-code” for your website, you might prefer a managed, GUI fileserver, too. I’m a big fan of DO’s services, so I’m gonna try it out tonight.