Files
Dominik cec0178e76 fix: encode dots in URL path segments to prevent browser resolution (#3308)
When editing a regex domain that is just "." (single dot), the browser
interprets it as a relative path component ("current directory") and
resolves it away before sending the request. The server receives an
empty string, causing "Invalid request: Specify item in URI".

This happens because encodeURIComponent(".") returns "." unchanged —
dots are unreserved characters per RFC 3986. The browser only normalizes
literal "." and ".." path segments, not percent-encoded "%2E".

Add utils.encodePathSegment() which wraps encodeURIComponent and also
encodes dots to %2E, then apply it in groups-domains.js (the reported
bug) and groups.js (which was also missing encoding entirely).

Fixes #3308

Signed-off-by: Dominik <dl6er@dl6er.de>
2026-03-25 07:04:28 +01:00
..
2025-10-04 08:58:29 +02:00
2026-03-16 22:06:16 +01:00
2026-03-16 08:55:20 +01:00
2026-03-16 08:55:20 +01:00
2026-03-16 08:55:20 +01:00
2026-03-16 08:55:20 +01:00
2026-03-16 08:55:20 +01:00
2025-06-27 21:19:40 +03:00
2026-03-16 08:55:20 +01:00
2025-04-23 20:50:12 +03:00
2025-05-15 18:17:31 +03:00
2026-03-16 08:55:20 +01:00
2026-03-16 08:55:20 +01:00
2025-05-12 18:46:36 +03:00
2026-03-16 08:55:20 +01:00