| 04:22 | <sideshowbarker> | I’m noticing some unexpected percent-encoding happening with the HTML checker service, and I’m wondering if it’s just some quirk unique to that, or if there’s something about percent-encoding that I’m misunderstanding |
| 04:23 | <sideshowbarker> | If you go to https://validator.w3.org/nu/ and enter this data URI:data:text/html;charset=utf-8,<%3Fxml-stylesheet type="text/css" href="style.css"?>into the Check by address text input |
| 04:24 | <sideshowbarker> | …then the request URL that the HTML checker uses is this:https://validator.w3.org/nu/?doc=data%3Atext%2Fhtml%3Bcharset%3Dutf-8%2C%3C%253Fxml-stylesheet+type%3D%22text%2Fcss%22+href%3D%22style.css%22%3F%3E |
| 04:24 | <sideshowbarker> | Notice the %253F |
| 04:25 | <sideshowbarker> | If I manually alter that part of the request URL to %25%3F, the HTML checker seems to fail to parse that data URI value as expected |
| 04:32 | <arai> | %253F is valid. that's %3F in the original URI, where the % itself is encoded as %25 |
| 04:36 | <sideshowbarker> | oh |
| 04:37 | <sideshowbarker> | d’oh of course — I see now |