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 issues were very large. This was filling logs quite quickly (I think it's possible to have "maxpost" bytes of data written to the log). Didn't want to disable all Warnings, so we patched NaviServer to log just a Warning of invalid UTF-8 but not include the data itself. But there may be a better way of dealing with this. Regards, David On Sat, 28 May 2022 at 18:45, Gustaf Neumann <neum...@wu.ac.at> wrote: > Dear all, > > The latest commits > - added the "multipart/form-data" handlingfor fallback charsets, > - provides an error code for invalid UTF-8 and > - adds support for the "_charset_" field for default charsets (see RFC > 7578, section 4.6). > > Also, the regression test got several more tests. > > I have still a bug report for ns_connchan (which i could not reproduce > so far), > if i find something to fix the next days, this will go as well into the > next > release, otherwise we are ready for rc2. > > all the best > >
_______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
