Open XMegamanX opened 6 years ago
Hum, we may have forgot to URL encode somewhere, in order to be accepted by a HTTP server. My tests:
Ok thanks. To be more precise, my file is on a S3. I add between "https://" and the "s3-xxxx" url the login:password@ trick to make it readable. It works with my other file but not for the one with special characters. Is there a link between the s3 access and the problem ? Thanks !
Is there a link between the s3 access and the problem ?
S3 can add another layer of issue, as we need to sign the URL, but I get the issue also without S3. We need to test with an S3 account too.
PS: there is no ETA for the fix on free support, we work on it when we have free time, let us know if you need to accelerate the development of the fix.
Hello ! I use Mediaconch for several month but today I wanted to check a file which name has some special characters "é" and a space. Mediaconch seems to considered the file as non existent. Is there a way to read url with special characters ? Thanks in advance