Hello Emmanuel!
Many thanks for that hint!
Emmanuel Cecchet schrieb:
I don't think that the issue is related to the charset at all, it is
mostly due to the parsing cache.
You've been right - me (partly see posting of Marc Herbert) wrong.
I don't know why an unknown request would be inserted there but that's
mostly the root cause.
Could you disable the parsing cache from your configuration file and
give it another try? If it works without the parsing cache, please
file a bug so that we can fix the cache.
It works without the parsing cache. For the record: The behavior is the
same on 2.10 and 3.0Beta1
Are you please so kind to file the bug by yourself since you surely can
describe the error more precisely than my person (not knowing what the
parsing cache is or what it does. :-) )
Best regards
Volker
--
====================================================
inqbus it-consulting +49 ( 341 ) 5643800
Dr. Volker Jaenisch http://www.inqbus.de
Herloßsohnstr. 12 0 4 1 5 5 Leipzig
N O T - F Ä L L E +49 ( 170 ) 3113748
====================================================
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
