-
Notifications
You must be signed in to change notification settings - Fork 846
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
Comments
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. |
Any update for this issue? i.e. any potential fix release? |
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. |
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? |
The Postman Console shows fully resolved values for each request which you can use instead of the history now. |
History should capture the actual URL rather than displaying the unparsed URL.
The text was updated successfully, but these errors were encountered: