Re: [naviserver-devel] ns_urlencode on Windows Naviserver

[Gustaf N. <ne...@wu...>]

Am 12.05.17 um 13:41 schrieb Brian Fenton:
>
> Thank you David
>
> So, assuming the documentation is incorrect 
> https://naviserver.sourceforge.io/n/naviserver/files/ns_urlencode.html 
> it seems that the API has been changed from AOLserver.
>
> Brian
>
Brian, are you worried about the literal comparison in a test case, or 
is there a deeper background?

Some more background: ns_urlencode in AOLserver was always incorrect in 
respect to the RFCs, which define different encodings for the "path" and 
the "query" part of an URL. Therefore many years ago, NaviServer added 
flags "-part" to specify the encoding (implementing an extension of 
RFC1738 (1994)).

In the (unreleased) tip version of NaviServer on bitbucket, i've updated 
the implementation to be in sync with valid RFCs (RFC 3986 for URIs and  
RFC 6265, cookie encodings). So if one compares the result of a tip 
version of NaviServer with the documentation of the released version, 
the results differ (btw., the example on the NaviServer man page is 
bad). See about the changes in the tip see e.g. [1] and the following 
postings.

-g

[1] 
https://sourceforge.net/p/naviserver/mailman/naviserver-devel/?limit=50&viewmonth=201703&viewday=22

-- 
Univ.Prof. Dr. Gustaf Neumann
WU Vienna
Institute of Information Systems and New Media
Welthandelsplatz 1, A-1020 Vienna, Austria