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

Postman is unescaping my query params #2538

Closed
hamid-elaosta opened this issue Dec 9, 2016 · 18 comments
Closed

Postman is unescaping my query params #2538

hamid-elaosta opened this issue Dec 9, 2016 · 18 comments
Assignees
Labels
Milestone

Comments

@hamid-elaosta
Copy link

  1. Postman Version: 4.9.1
  2. App (Chrome app or Mac app): Linux app
  3. OS details: Ubuntu Gnome 16.04 x64
  4. Is the Interceptor on and enabled in the app: No
  5. Did you encounter this recently, or has this bug always been there: Recent/Never tested before
  6. Expected behaviour: Don't unescape manually encoded query params
  7. Console logs (http://blog.getpostman.com/2014/01/27/enabling-chrome-developer-tools-inside-postman/ for the Chrome App, View->Toggle Dev Tools for the Mac app): Nothing shown
  8. Screenshots (if applicable)

if I make a query to my API as follows:

/?number=%2b18005552222

I expect Postman to send as-is. However, Wireshark shows that postman has decoded the %2b to +.
This is a problem because + in a query string is special character for space " ", and is then decoded incorrectly on the server.

If I perform the same in Chrome, It is sent as-is. Proven again using Wireshark that the query is sent as-is (still encoded).

@benjamw
Copy link

benjamw commented Dec 9, 2016

I'm having a similar issue. Mine is regarding following redirects. My redirects have URL encoded chars like %2b and %40 which are incorrectly getting converted. So it seems that Postman is converting those at a low level.

@benjamw
Copy link

benjamw commented Dec 9, 2016

Possible duplicate of #2529

@albertogiunta
Copy link

Having identical issue here!!

@Nirvaner
Copy link

Windows 10, postman not chrome plugin - as windows application, I'm having a similar issue

@sdnts
Copy link

sdnts commented Dec 13, 2016

Guys, we are looking into this, I'll let you all know when a fix is out. Thanks for letting us know.

@mooglemoogle
Copy link

Some more info: I'm running Windows 7 and v4.9.2 of the standalone app. When I first attempted to diagnose this issue, I used Fiddler to intercept the requests. Fiddler works by adding a system proxy. When the request went against that proxy, the issue disappeared and the URL was encoded properly.

@tobeliketree
Copy link

tobeliketree commented Jan 9, 2017

Any updates on this? I logged #2517 and no movement on that either. this has been really disruptive to my workflows. Can someone update?

@SamvelRaja
Copy link

@hamid-elaosta @benjamw @albertogiunta @Nirvaner @mooglemoogle @tobeliketree
The issue has been fixed in our latest canary(4.9.4-canary.1) release,
can you guys switch to that version an check the same?
On additional note we are using the whatwg's url parser algorithm.

@benjamw
Copy link

benjamw commented Jan 25, 2017

How do I update to canary if I'm using the standalone app?

@hamid-elaosta
Copy link
Author

@SamvelRaja thanks for the update, there's not much I can do with the osx binary you linked though, I run Linux.

@sdnts
Copy link

sdnts commented Jan 25, 2017

Guys, here are links for the Canary builds:

OSX: https://dl.pstmn.io/download/channel/canary/osx_64
Windows 32-bit: https://dl.pstmn.io/download/channel/canary/windows_32
Windows 64-bit: https://dl.pstmn.io/download/channel/canary/windows_64
Linux 32-bit: https://dl.pstmn.io/download/channel/canary/linux_32
Linux 64-bit: https://dl.pstmn.io/download/channel/canary/linux_64

@benjamw You'll need to download the Canary build for your platform. When you sign in, all your collections would be synced in (if you use Sync).

@gmanenti
Copy link

gmanenti commented Jan 25, 2017 via email

@hamid-elaosta
Copy link
Author

@madebysid Thanks, didn't get a chance to test today but will do as soon as poss.

@hamid-elaosta
Copy link
Author

@madebysid Downloading Linux 64-bit now.

FYI, you link to the 32bit for both 32/64 Linux versions, it had me tearing my hair out for a while until I realised I was trying to run the 32bit version and I don't have the 32bit libs.

@SamvelRaja
Copy link

SamvelRaja commented Jan 31, 2017

@hamid-elaosta Thanks for your response. Updated the link aswell. Can you confirm it is fixed 😄

@SamvelRaja SamvelRaja added this to the 4.10 milestone Jan 31, 2017
@SamvelRaja SamvelRaja self-assigned this Feb 6, 2017
@hamid-elaosta
Copy link
Author

hamid-elaosta commented Feb 8, 2017

@SamvelRaja Apologies for the delay, just finally had the chance to test and I can confirm it's fixed in the canary build you linked.

@SamvelRaja
Copy link

Closing this, as the fix is rolled out in the 4.10.2 version of the app 😄

@kishoretangudu
Copy link

  • is transforming as space " " in the request URL. is it solved? I am using postman 5.5.4 version. Please tell me. Anticipating quick reply.

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

No branches or pull requests

10 participants