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

History is totally useless if using variables in URL #1229

Closed
yeshodhan opened this issue Jul 9, 2015 · 5 comments
Closed

History is totally useless if using variables in URL #1229

yeshodhan opened this issue Jul 9, 2015 · 5 comments
Labels

Comments

@yeshodhan
Copy link

History should capture the actual URL rather than displaying the unparsed URL.

screenshot 2015-07-08 19 09 03

@BrakTalk
Copy link

I second this. We have multiple environments as code gets promoted towards a release. Not being able to tell which environment was accessed is a rather profound issue for us.

@BrakTalk
Copy link

Any update for this issue? i.e. any potential fix release?

@a85
Copy link
Contributor

a85 commented Nov 9, 2016

We don't store actual values due to security issues. We are thinking about storing the environment value that the request was sent with along with tab specific environments that should have the same effect as storing variable values while also ensuring that sensitive values don't show up.

@a85 a85 removed their assignment Dec 21, 2016
@yeshodhan
Copy link
Author

If you can save environment values, why not save the urls? Atleast provide an option in settings to enable or disable variable replacement in history?

@sdnts sdnts added the feature label May 25, 2017
@a85
Copy link
Contributor

a85 commented Nov 11, 2017

The Postman Console shows fully resolved values for each request which you can use instead of the history now.

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

5 participants