I observed that a specific Postman collection, which runs successfully in other workspaces, is failing to execute requests when used in a workspace with Git integration. Is there a known issue or common explanation for this, particularly regarding Git’s interaction with or potential overwriting of proxy configurations?
Do you any any further information or visual examples showing the issue?
Is that another git connected Workspace or a Cloud Workspace? Are you setting the request to a specific endpoint? Are there environment or any other variables used? Does this use any Auth helpers or request headers?
It’s tough to know what is happening for you, given the details provided.
My Postman collection ‘A’ works as expected in non-Git integrated workspaces. However, after importing it into a workspace connected to Git (and operating within a Git branch, not the cloud view), requests from this collection consistently fail. This behavior is reproducible, as confirmed by testing in a third, non-Git workspace where the collection also runs successfully. I tested the same exact request.
@Danny Dainton
I’ve quickly pinpointed a key issue: in the Git-integrated workspace, if a request has an x-www-form-urlencoded body and an explicit Content-Type: application/json header, the Content-Type is overridden to application/json.
However, in a non-Git workspace, with the identical Content-Type: application/json header, the Content-Type remains application/x-www-form-urlencode. Also Postman runtimes are different.
Git workspace headers logs:
"Request Headers": {
"accept": "application/json",
"content-type": "application/json",
"user-agent": "PostmanRuntime/1.3.4",
....
},
Not VCS headers logs:
“Request Headers”: {
“accept”: “application/json”,
“content-type”: “application/x-www-form-urlencoded”,
“user-agent”: “PostmanRuntime/7.53.0”,
....
},