barry@zope.com (Barry A. Warsaw) writes: > If the data is encoded in a non-ascii character set, wouldn't (or > shouldn't) the Content-Type: header include a charset="xxx" parameter? Yes, but none of the browsers does that. The urlencoded form doesn't really support charsets in the first place. The multipart/form-data could, but the browsers don't provide the information (in violation of RFC 1867). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4