Dear all,
on sourceforge is the release of NaviServer 4.99.22 [1] available
The code was tested with Ubuntu 20.04, Rocky Linux 8.4, OpenBSD 6.9
(clang),
FreeBSD 13.0-CURRENT, macOS 11.5.2 (Intel and M1).
The following people have contributed to this release:
Gustaf Neumann
Ibrahim
On 25.08.21 11:07, Wolfgang Winkler wrote:
Thank you for your answer. I've missed the corresponding RFC 3986 part
you quoted.
We have a client who, for some reason, got an error, when the @ sign
of emails in the query section was not escaped. It has been solved on
his side, but I was not
Dear Maksym,
On 24.08.21 02:39, Maksym Zinchenko wrote:
But lately, user logs in start working and randomly redirected back to
the login screen because data in db is not the same as in cache,
when you have values from the DB cached, then whenever the DB changes,
you have to flush the cache
Dear Wolfgang,
according to RFC 3986, the at-sign should not be encoded, neither in the
path segments, nor in the query components.
For querycomponents the right parameter for ns_urlencode is
ns_urlencode -part query a@b
The full query parameter pair should be encoded with
set
Dear List!
When using ns_urlencode, I've noticed, that the "@" sign will not be
percent encoded, unless "-part oauth1" is stated:
ns_urlencode t...@test.com
t...@test.com
ns_urlencode -part oauth1 t...@test.com
test%40test.com
What is the correct way to encode URL params, e.g. in
