On Tue, 01 May 2012 18:12:36 -0700, Evan Jones <evanj@...> wrote:
> … this seems contradictory: Encode using RFC 2388, but do not using the
> encoding suggested by the RFC. Worse, no browser actually follows the
> RFC (e.g. they all use UTF-8 encoded parameter values), so that doesn't
> seem like the right answer. Is there a way out of this mess?