Encountering 404 error in URL's with special characters

[Richard Moss]

I've logged a bug for where file names aren't using UTF-8 encoding to look at in a subsequent release. Sorry I couldn't get all your issues fixed, but it's better to concentrate on the more serious bugs. I'll update this thread as soon as I have more information (or a fix!) regarding the file name bug.

Regards;
Richard Moss

[matrix1999]

Hi, are you still planning to have this addressed in a future release?

[Richard Moss]

Hello,

My honest answer is I have forgotten if this is resolved or not. If you have an example where this is occurring then please provide details and I'll look into it.

Regards;
Richard Moss

[matrix1999]

Hi thanks for your prompt reply.  The URL I tried was https://thetrove.net/Magazines/Jeu%20de%20R%C3%B4le/

I think it failed on the "ô" character

[Richard Moss]

Hello,

Thanks for the example URL, I'll look into it and get back to you.

Regards;
Richard Moss

[Richard Moss]

Hello,

Well, that was a fun little excursion. Basically, the web server was returning the Location header in a 301 redirect in UTF8 but I was expecting ASCII and so was corrupting the URL, thus causing a 404 as WebCopy tries to access something completely invalid. I've got a fix in place but unfortunately it may be a short time before it is publicly accessible as I'm having trouble with a particular brand of antivirus flagging our files as malicious and I've yet to hear back from them regarding the issue.

Thanks for the example which helped to pin down the issue!

Regards;
Richard Moss

[matrix1999]

* thumbs up *

Thanks for looking into the matter for me and I am glad to hear that you have identified a solution.  If there is any particular build that you want me to try, let me know and I am happy to hop on it.

Thanks once again, sir!