Describe the bug
When setting the "Default URL" parameter of an "External environment" session launcher to a string containing ? (and possibly other special characters), this is percent-encoded in the session iframe src.
This is an issue because servers such as VS Code accept parameters with /?par1=val1&par2=val2. For example, trying to launch VS Code with a default folder via /?folder=/some/folder results in /%3Ffolder=/some/folder, causing it to fail.
Link to project
https://renkulab.io/p/matteo.secli/nedoqs-tutorials-2026
To Reproduce
Steps to reproduce the behavior:
- Go to the linked project and copy it
- Edit the environment of the "Visual Studio Code" session launcher
- Provide
/?folder=/home/jovyan/work as "Default URL"
- Launch the session
- You eventually get a "Not found" error in the session iframe
- Inspect the iframe and change
%3F to ? in the src field
- Now VS Code loads in the desired folder
Expected behavior
"Default URL" parameters should not be percent-encoded.
Describe the bug
When setting the "Default URL" parameter of an "External environment" session launcher to a string containing
?(and possibly other special characters), this is percent-encoded in the session iframe src.This is an issue because servers such as VS Code accept parameters with
/?par1=val1&par2=val2. For example, trying to launch VS Code with a default folder via/?folder=/some/folderresults in/%3Ffolder=/some/folder, causing it to fail.Link to project
https://renkulab.io/p/matteo.secli/nedoqs-tutorials-2026
To Reproduce
Steps to reproduce the behavior:
/?folder=/home/jovyan/workas "Default URL"%3Fto?in thesrcfieldExpected behavior
"Default URL" parameters should not be percent-encoded.