I like the solution suggested by Andrew as well. This should allow an
easy transition of existing code without sacrificing security.
Am 07.10.24 um 17:59 schrieb Andrew Piskorski:
On Mon, Oct 07, 2024 at 12:54:32PM +0200, Gustaf Neumann (sslmail) wrote:
However, there are many cases, where ex
Hi all!
When compiling the current version of nsdbg from
https://github.com/naviserver-project/nsdbpg/tree/main
I get the error:
tclcmds.c:1635:37:error: expected ‘)’ before ‘PRITcl_Size’
sprintf(segment_pos, "%d, %"PRITcl_Size", '%s')",
^~~~
)
I locally changed the line 1635 t
mmits/6f7b322d0f45daa2154d702ca763442bb2be9fac
all the best from Maui,
-gustaf
On 04.01.23 15:19, Wolfgang Winkler via naviserver-devel wrote:
Hello!
When we try to use custom tags with attributes, we encounter a
problem when passing html strings, e.g:
proc::dummy_tag_proc {params} {
return[ns_set
ister.html
Brian
----
*From:* Wolfgang Winkler via naviserver-devel
*Sent:* Wednesday 4 January 2023 2:19 pm
*To:* Navidevel
*Cc:* Wolfgang Winkler
*Subject:* [naviserver-devel] ns_adp_registerproc and attributes
Hello!
When we try to use custom tags with attributes, we encount
Hello!
When we try to use custom tags with attributes, we encounter a problem
when passing html strings, e.g:
proc::dummy_tag_proc {params} {
return[ns_set array$params]
}
ns_adp_registerscript dummy_tag ::dummy_tag_proc
Outputs:
title {"}
Everything after the first ">" is truncated. Is t
Hi!
We use
ns_set update [ns_conn outputheaders] Content-Disposition "attachment;
filename=\"${filename}\""
for downloading and
ns_set update [ns_conn outputheaders] Content-Disposition
"filename=\"${filename}\""
for viewing files
Am 15.07.22 um 16:50 schrieb Maksym Zinchenko:
Hello, I
Hi!
We are using Debian Buster without any problems.
Here are some details:
cat /etc/debian_version
10.12
dcweb:nscp 1> info patchlevel
8.6.11
dcweb:nscp 1> ns_info patchlevel
4.99.23
This is our configure script:
# --with-openssl=/usr/local assumes a manually installed openssl
version. Fo
Hello all!
We encountered a small problem with ns_parseurl:
When parsing
ns_parseurl "/test/index?url=http://www.test.at";
everything works fine.
With
ns_parseurl "index?url=http://www.test.com";
We get "Could not parse URL "index?url=https://www.test.com": invalid
scheme"
* ns_parseurl
Gustaf Neumann:
Forwarded Message
Subject:Re: [naviserver-devel] No notifications with webpush::send
Date: Thu, 9 Dec 2021 11:43:44 +0100
From: Gustaf Neumann
To: Wolfgang Winkler via naviserver-devel
On 09.12.21 09:33, Wolfgang Winkler via naviserver
viserver-git--with-openssl=/usr/local/openssl--with-tcl=/usr/local/lib/--enable-threads
But naviserver still uses the packaged openssl version:
# ldd nsd/nsd
libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1
Regards,
Wolfgang
Am 07.12.21 um 17:16 schrieb Gustaf Neumann:
On 07
Hi list!
We are trying to send webpush messages with the naviserver webpush moule
(webpush::send). It used to work fine a few months ago.
Now we have the following problem: When sending an empty push message with:
setmessage{}
setret [webpush::send \
-subscription $subscription_lis
s as variable names).
On 16.11.21 16:39, Wolfgang Winkler via naviserver-devel wrote:
the fix worked, thank you Gustaf! But we still have a problem with
emojis when writing them to the database. The error we get is:
Database operation "dml" failed (exception ERROR, "ERROR:
16:39, Wolfgang Winkler via naviserver-devel wrote:
the fix worked, thank you Gustaf! But we still have a problem with
emojis when writing them to the database. The error we get is:
Database operation "dml" failed (exception ERROR, "ERROR: invalid
byte sequence for encodi
Hello all,
the fix worked, thank you Gustaf! But we still have a problem with
emojis when writing them to the database. The error we get is:
Database operation "dml" failed (exception ERROR, "ERROR: invalid byte
sequence for encoding "UTF8": 0xf0 0x9f 0x98 0xff
when trying to write the emo
Dear all!
We face some issues with certain UTF-8 characters, e.g. this one:
https://emojipedia.org/grinning-face-with-big-eyes/.
When we set "charset" to "utf-8", everything works as expected, except
the output of various emojis.
setstr "Test smiley: 😃öüäÖÄÜß"
ns_return 200"text/html; chars
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
http://tes
Dear Gustaf,
thanks for the speedy fix. We've cherry picked the commit for 4.99.19
and it works flawlessly.
Cookie handling has become a catch up game lately, as browser vendors
are getting more and more creative without a proper standardization process.
Regards,
wiwo
Am 31.08.20 um 12:54
Hello!
We are using "ns_setcookie" with the flag "-samesite". If used with
"-samesite none", the SameSite value of "None" is not passed to the
browser. An empty "SameSite" value is different from "SameSite=None", at
least in Chromium based browsers.
I checked the source code:
https://bitbuc
18 matches
Mail list logo