Hacker News new | past | comments | ask | show | jobs | submit
Why not?
Because not accepting it would break backwards compatibility and the general expectation that in HTTP the sender can use any non-obscure encoding and the receive has to deal with it. Of course there is no need for the receiver to implement special uppercasing for each encoding - more sensible would be to convert it to UTF-8 at the earliest opportunity.
It's 2026, I think legacy Windows code pages are obscure at this point.
Not on the web they aren't.
loading story #50561861