Thanks Gustaf - the errorCode will be very handy to trap these encoding
errors.
We're using the per-server "formfallbackcharset" without issue at the
moment. Working well.
One problem we encountered is the Warnings logged when invalid UTF-8 is
encountered.
Some of the POSTs causing encoding issue
i agree, this might be a lot of logging, especially when the decoded
strings are long.
Not sure, what the best approach of this is
- an configuration parameter LogInvalidUTF8warnings to deactivate these
messages (default true)
- an configuration parameter NrInvalidUTF8warnings to limit these
m
