-
![](https://image.nostr.build/46748cf4fa614b75109ead7b70927e1ab8ea686fd3af03a12027e3414b9fe572.jpg)
@ Anthony Accioly
2025-02-14 12:25:42
Many thanks for getting back to me on this nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpr3mhxue69uhhxct5v4kxc6t5v5hxs7njvscngwfwvdhk6tcpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsk7wj75, this makes a lot of sense. What if I always redirect to a file with proper extension (I.e., even if the user requests /sha256 I redirect it to a url with /sha256.extension)? In your option would this be enough to mitigate the "users cutting and pasting URLs from the client" problem? I.e., they would be always accessing a public URL with proper extension.