The interesting part here is the \uD801\uDFFE - that's a UTF-16 surrogate.
The behaviour in this case is undefined as per the URL specification^5, where the input to the url parsing algorithm is a scalar value string^2 (meaning a string containing neither leading nor trailing surrogate characters).
url/README.md states:
resources/urltestdata.json contains URL parsing tests suitable for any URL parser implementation.
Therefore, the suite should only test behaviour defined in the url specification^4.
I would like to hear the thoughts of more qualified people on this before I make a PR for it (:
urltestdata.json
contains the following test:The interesting part here is the
\uD801\uDFFE
- that's a UTF-16 surrogate.The behaviour in this case is undefined as per the URL specification^5, where the input to the url parsing algorithm is a scalar value string^2 (meaning a string containing neither leading nor trailing surrogate characters).
url/README.md
states:Therefore, the suite should only test behaviour defined in the url specification^4.
I would like to hear the thoughts of more qualified people on this before I make a PR for it (: