hi there, thanks for that. We will take a look as soon as we are able. Apologies for for the disruption, but we’re glad to be alerted to this behaviour for Netlify Large Media! That is definitely helpful for us to know about
It looks like you activated the feature right while we’re making a long coming change from netlify.com to netlify.app for internal subdomains. I’m very sorry for the disruption. You can read more details about this change in this other thread: Changes coming to Netlify site URLs
If you change netlify.com in your lfs configuration to netlify.app, it would work as expected.
hmm, that isn’t what we had expected! We are going to do a little digging and try and figure this out. We’ll get back to you here as soon as we can with more information or questions. Thanks again for your patience.
Hey @thewellington, we are actively working on this and hope to have a code change that’ll fix this published soon. I totally get that this is less than ideal - we’ll update you as soon as we have any news.
those are good questions - it may be that something got a bit muddled up while you were troubleshooting earlier. The Support Engineer who knows most about LFS can take a look when he is back around, hopefully we can get you some definite answers by tomorrow.
As a general rule, any special character (and that includes spaces, which get treated like special characters when they are in filenames) are a no-no, really, as they don’t get handled well or consistently by filesystems, as a rule. We encourage all-lowercase and no spaces to minimize weird behaviour