Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URL Parse error after upgrading to 9.3 #7603

Closed
1 task done
fasigpt opened this issue Jun 27, 2024 · 8 comments
Closed
1 task done

URL Parse error after upgrading to 9.3 #7603

fasigpt opened this issue Jun 27, 2024 · 8 comments
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer

Comments

@fasigpt
Copy link

fasigpt commented Jun 27, 2024

Expected Behavior

API calls should be allowed if the URI contains '@'

Actual Behavior

Unable to make API calls if the URI has special character like @

Throws exception new Url(): failed to parse auth in url ${urlStr}

Ex: https://youdomain/api/validateuser/[email protected]

Reproduction Steps

Example

Ex: https://youdomain/api/validateuser/[email protected]

Is there an existing issue for this?

Additional Information

Insomnia Version

9.3

What operating system are you using?

Windows

Operating System Version

Windows 11

Installation method

windows msi

Last Known Working Insomnia version

No response

@fasigpt fasigpt added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Jun 27, 2024
@subnetmarco
Copy link
Member

We are looking into this issue.

@shwethavshenoy
Copy link

Same. Any ETA on the fix?

@gatzjames
Copy link
Contributor

Thanks for the feedback. Closing as this was fixed in 9.3.1

@deefdragon
Copy link

Not sure if its this bug resurfacing, or a different bug, but I am encountering this error when I attempt to put a file to an s3 signed upload URL, and have a pre request/post response script. It does not trigger if there are no scripts.

@subnetmarco
Copy link
Member

@deefdragon can you update to latest 9.3.3 and try again? If it still happens, we will look into this again.

@deefdragon
Copy link

I did just test on 9.3.3 and encountered it yes.
As a note, if I try to put a script in after-response specifically, it appears that the request finishes. Just the script does not run. Not sure how that impacts things.

@ihexxa
Copy link
Contributor

ihexxa commented Mar 4, 2025

Finally found a solution and working on this now.

@ihexxa
Copy link
Contributor

ihexxa commented Mar 12, 2025

The fix will be shipped with v11.

@ihexxa ihexxa closed this as completed Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer
Projects
None yet
Development

No branches or pull requests

6 participants