Don't laugh.

Due to the painfully short MAX_PATH on Windows, we have a bunch of jobs with single-character job names, and user-friendly display names. Since that limits the number of jobs we can create for Windows, I tried creating a job with a valid Unicode character as the job name.

I got a 404 from this, when it forwarded to the job config - however, the job WAS created. Similarly the job shows in the view, but clicking it throws a 404 - but manually editing the URL works.

It seems Unicode characters are stripped from whichever method creates a /job/JOBNAME/ url? e.g. links which should read http://localhost:8080/job/%F0%9F%90%A7/ instead read http://localhost:8080/job//