Not sure if this helps you - it may be entirely expected behaviour, but I
attached gbp to the nsproxy process and got a backtrace from the 2 test
cases I mentioned, immediately after the "ns_proxy eval...".
In the case with no hang the nsproxy process is waiting in RecvBuf:
#0
Dear Brian,
a short look into the code, at the two different
implementations (and how much they differ) would have avoided this wrong
assumption.
On top of that, as Gustaf suggested, using the "-part path" option you can
obtain the full URL properly converted.
The main
Thanks Gustaf
An issue arose during migration testing which was breaking some of our existing
AOLserver code, then when I saw the documentation issue, I thought best to
check with the list that maybe there was an issue with the Windows version.
I'll dig into our code and see what the problem is
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
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
From: David Osborne [mailto:da...@qcode.co.uk]
Sent: 12 May 2017 12:36
To:
---
Welcome to tlc_erp running at /usr/lib/naviserver/bin/nsd (pid 10339)
NaviServer/4.99.16d5 for linux built on May 4 2017 at 16:39:38
Tag: tar-4.99.16d5
tlc_erp:nscp 1> ns_urlencode
http://www.aolserver.com/redirect.adp?url=http://www.aol.com=1,2,3
Hi Maurizio
I really don't know. I don't have access to a Linux installation to check. Are
you suggesting that the API may have changed since AOLserver?
Brian
From: Maurizio Martignano [mailto:maurizio.martign...@spazioit.com]
Sent: 12 May 2017 12:31
To: naviserver-devel@lists.sourceforge.net
Dear Brian,
Is this really a "Windows Naviserver" issue or is it a matter
of a new implementation of the function, different from what was previously
done in Aolserver?
The two implementations seem to me quite different.
Thanks a lot,
Maurizio
From: Brian Fenton
I think there might be a problem with ns_urlencode on Windows Naviserver.
I just ran this example (taken directly from the documentation):
ns_urlencode
http://www.aolserver.com/redirect.adp?url=http://www.aol.com=1,2,3
And the result was unexpected:
