I believe this is a bug. When saving my response, environment variable tokens are preserved for Headers, however any such token on the URL of the request is fully resolved to its literal value. This means that environmental details, which you’d like to keep hidden when publishing your documentation with no environment, are disclosed in the code samples of the published documentation.
Please see the attached screen-shots. The first is the response itself. You can see that details of the request are encoded as tokens for headers and the URL. The second is the saved response. Tokenization is preserved for the headers, but the url shows the fully resolved target url, which you may not wish to disclose in your public documentation.
Edit: As I’m working with the Postman documentation feature, I’m finding that the Save Response feature is problematic in this respect in many areas. I can’t pin it down, but sometimes it replaces variable references with their literal values and sometimes it leaves the variable references in place. What I have found is that I need to go through my saved responses manually before I publish and restore the variable references so that they show up as such in the published documentation. Actually, when I restore these references, I need to code an “artificial syntax”, that is {reference} rather than {{reference}} because if I do the latter I will revisit the response at a later point and find that Postman has reverted the variable reference back to its literal contents.
If someone from Postman sees this - can you please correct your Save Response feature (or at least provide an option) so that it preserves variable references from the original request. Thank you.
