fetch should take care of percent encoding the url

Issue description

Currently the administrator has to take care of encoding the url passed to fetch, e.g. if a password contains an @ or a question mark, it is necessary to urlencode it. But this should not worry the administrator.

Rejection comment

This could work except in corner cases, e.g. a password containing a percent followed by two digits. But it seems clearer and easier to not do anything right now and let the caller be responsible for a potential encoding.

Reporting date

2025-04-17

Reported by

Robert Cerny

Rejection date

2025-04-17

Rejected by

Robert Cerny

Work sessions

Start	2025-04-17T10:01:48
End	2025-04-17T10:34:42
Participant	Robert Cerny

Helpful webpages

stackoverflow.com/…oid-double-encoding-uri