Lambda Function URL converts encoded slashes

If you call an Lambda Function URL with encoded slashes it appears that it converts them before passing it to the function itself. So if you have a url .../iiif/2/ad-test%2Fph_000207/info.json the event path becomes /iiif/2/ad-test/ph_000207/info.json. I think this must be a bug/oversight, because the API Gateway in similar usage would retain the encoding.

Thanks,

Joseph