On Fri, May 10, 2024 at 1:51 PM Bachir Bendrissou <babendris...@gmail.com> wrote:
> Hi Jeff, > > Thank you for your reply. > > The colon has nothing to do with the issue. If we remove the colon, the > issue still persists: > > *curl* "a;bc@xyz" > curl: (6) Could not resolve host: xyz > > *wget* "a;bc@xyz" > wget: unable to resolve host address ‘a;bc@xyz’ > > *wget* "abc@xyz" > wget: unable to resolve host address ‘xyz’ > > So, when the semicolon is included in *userinfo*, wget treats *userinfo* > as part of the hostname. You can replicate this after disconnecting from > your network first. > My bad, I was only answering the question, "Why is the semicolon not allowed in userinfo, despite the fact that other special characters are allowed?" I did not try to figure out what was wrong with the script. Jeff
