So far two people have had the issue where they try to have a username/password with a special character in the username(and possibly password) which leads to k6 not parsing the URL correctly, which is what it should do - we can't know what the intention of someone is, that is why the special characters exist ;).
The solution is to wrap it in encodeURIComponent and I think we should update this examples to show that
case 1 and issue from it and today case 2
So far two people have had the issue where they try to have a username/password with a special character in the username(and possibly password) which leads to k6 not parsing the URL correctly, which is what it should do - we can't know what the intention of someone is, that is why the special characters exist ;).
The solution is to wrap it in encodeURIComponent and I think we should update this examples to show that
case 1 and issue from it and today case 2