Noah Slater wrote:
...
* Is there a default encoding for parameter values, or in fact any other part
of this header. I could not find anything in the draft which would indicate
there is a default. Could this cause problems?
...
The encoding is restricted by HTTP, thus, depending how you read
RFC2616, to ASCII or ISO-88591-1 at best.
That's why an extension mechanism is needed anyway; the draft uses
RFC2231-based encoding.
BR, Julian
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf