We found the issue on our current server implementation through that bug: https://github.com/skddc/rs-backup/issues/11 The test suite doesn't cover what should happen when requesting a valid resource with wrongly encoded UTF-8. It should probably be a 404