[Web-SIG] parsing of urlencoded data and Unicode
Manlio Perillo
manlio_perillo at libero.it
Tue Jul 29 21:50:45 CEST 2008
Deron Meranda ha scritto:
> [...]
>> But, at this point, can one consider the content of form post to be encoded
>> "text" string?
>>
>> Or it should be considered encoded "byte" string?
>
> Both/either.
>
> I'd say follow the RFC, but perhaps allow a caller to provide
> an override default. So yes, you should assume an encoded
> string if the subpart has a text/* Content-Type, or if it has no
> content type at all (which must then be assumed to be text/plain
> US-ASCII). That is the intent of the MIME text/* media type
> after all; that it should be interpreted as a character string
> and not a byte string.
>
> In other cases, I would say returning a byte string is the
> correct thing to do.
>
I'm not sure to understand.
If you want non text data in the POST request body, you can use the file
control.
I can't really see use cases of normal input fields having byte strings.
> [...]
Manlio Perillo
More information about the Web-SIG
mailing list