Issue Description When a file/folder (FileNode) is created through the JMAP API (FileNode/set), the resulting object’s <D:href> in subsequent WebDAV PROPFIND responses contains the raw, unencoded name (including literal spaces and raw UTF-8 bytes for non-ASCII characters) instead of a properly perce…

Thanks for the reply, any idea on the next release date?

[image] stalwart: Fixed in v0.16.19 thanks but I still see the same problem I did update to v.0.16.19 [image]

just to be on the same page xxxx@mail:~# cd /opt/stalwart cp -r etc etc.bak-$(date +%Y%m%d_%H%M) docker compose pull docker compose up -d sleep 5 docker exec stalwart /usr/local/bin/stalwart --version [+] pull 7/7 :check_mark: Image stalwartlabs/stalwart:v0.16 Pulled …

Based on your screenshot, Stalwart is properly percent encoding the JMAP resources but your client is not decoding them. Have you tried deleting the DAV mount and adding it again? If so please send the raw PROPFIND response.

the client is bulwark web based via firefox could it be the source of the display bug?

It depends. If the screenshot is Bulwark and those files were created via WebDAV, then it is a Stalwart bug (but not the same bug you originally reported). If the screenshot comes from your WebDAV client and the files were created using Bulwark then it’s likely a WebDAV client bugs but we need logs …

I went on and tested Winscp → showing all file names correct using the webdav client. Also RaiDrive shows file names correct, so could it be the bulwark bug?

can you give me the exact logs you want to see so I can generate?

WebDAV PROPFIND <D:href> is not percent-encoded for FileNode objects created via JMAP, breaking WebDAV clients (spec violation of RFC 3986)

Issues

stalwart August 23, 2026, 6:46pm 2

Fixed in v0.16.19 (yet to be released).

WebDAV hrefs not URL-encoded when 'exported' via vandelay

Topic		Replies	Views
WebDAV hrefs not URL-encoded when 'exported' via vandelay Issues	4	48	August 24, 2026
Content sniffing should be used on text files to determine media type Issues	3	48	June 14, 2026
CalDAV: calendar-query REPORT returns empty calendar-data for JMAP-created events Issues	1	51	July 19, 2026
JMAP download returns 404 for directly-shared FileNode blobs despite mayRead = true (works when shared via parent folder) Issues no-ai	3	38	May 25, 2026
Email/query returns position: 0 for anchored queries → clients stuck on the first page (20 messages) Issues	2	42	June 18, 2026

WebDAV PROPFIND <D:href> is not percent-encoded for FileNode objects created via JMAP, breaking WebDAV clients (spec violation of RFC 3986)

Related topics