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

Encoding error in exporting requests from Postman #11934

Closed
1 task done
rishirdua opened this issue Apr 18, 2023 · 4 comments
Closed
1 task done

Encoding error in exporting requests from Postman #11934

rishirdua opened this issue Apr 18, 2023 · 4 comments
Assignees

Comments

@rishirdua
Copy link

Is there an existing issue for this?

  • I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

I have an entity with id: urn:li:foo:62324 To make a GET call, I set "urn%3Ali%3Afoo%3A62324" in the URL and it works fine.

This gets translated to "urn%253Ali%253Afoo%253A62324&" in the exported CURL

This means the percentage sign is getting encoded, which I don't want.

It seems Postman is making a different curl call from what it is exporting.

I'm fairly confident this is a new issue since this used to work fine.

Steps To Reproduce

  1. Open a new request tab
  2. Make a GET call to http://linkedin.com/urn%3Ali%3Afoo%3A62324
  3. Look at the corresponding curl generated.

Screenshots or Videos

See screenshot
postman-bug

Version 10.12.13
UI Version: 10.12.13-ui-230411-0412
Desktop Platform Version: 10.12.13 (10.12.13)

Operating System

Mac

Postman Version

10.12.13

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

@dhwaneetbhatt
Copy link

Thanks @rishirdua for reporting this. We're looking into it and will keep this thread updated.

@dhwaneetbhatt dhwaneetbhatt self-assigned this Apr 18, 2023
@rishirdua
Copy link
Author

Hey @dhwaneetbhatt do you happen to have an ETA for this?

@dhwaneetbhatt
Copy link

Hey @rishirdua this will be fixed in the May monthly update which should roll out sometime after 15th May. Will update this thread when it starts rolling out.

@dhwaneetbhatt
Copy link

@rishirdua this issue is fixed in the latest (v10.14) version of Postman. Feel free to reopen this with additional details if the problem still persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants