Hi,
>> The HTTP RFC only allows ASCII in the headers. > > In header *names*, but anything can fit in a value, except LF. Ah, sorry about that, I really thought values are restricted as well. > It is possible to filter on this if you can write these characters in > the configuration. We don't have a way to encode characters in the > config at the moment (which is one reason why I want to update the > config format in 1.6). So if I understand correctly it *does* work if the configuration contains the (multibyte) character as-is, the only problem is that we can not represent it in the configuration in an escaped form like \xE4B888? Is that what you mean? Thanks, Lukas
