Hi Gustaf, We've been testing *4.99.24 rc1* and it seems pretty solid so far. Thanks for all the work that went into it.
One change of behaviour that is causing us issues is the handling of invalid UTF8 characters. We have a system which regularly POSTs data to NaviServer - sometimes (for reasons we're looking into) the POST'ed data received by NaviServer can contain urlencoded characters which don't exist in UTF8 ( for example *%9C* instead of *%C5%93*). In previous versions of NaviServer, this causes an invalid character to be embedded in the data when we save it. Now, in version 4.99.24 we, rightly, get the warning "*Warning: decoded string is invalid UTF-8:*". But the additional behaviour is that the entire form variable seems to be dropped. I just wanted to query if that is the intended behaviour? I've seen some servers convert such invalid characters to *\ufffd* (\ufffd being "replacement character" - "used to replace an incoming character whose value is unknown or unrepresentable in Unicode") - but not sure which is the correct behaviour. Regards, Dave
_______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
