You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a request is made with empty string value in header wrong curl code is generated. It doesn't add ; at the end.
To Reproduce
Steps to reproduce the behavior:
Set request url to localhost/users
Set header field name to tenant and leave it empty
Click code
you will get: curl --location --request GET 'localhost/users' --header 'tenant: '
which should be: curl --location --request GET 'localhost/users' --header 'tenant;'
Expected behavior
curl --location --request GET 'localhost/users' --header 'tenant;'
Screenshots
If applicable, add screenshots to help explain your problem. Please make sure the screenshot does not contain any sensitive information such as API keys or access tokens.
App information (please complete the following information):
App Type [Native App]
Postman Version [7.34.0]
OS: [macOS Catalina 10.15.5]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I wanted to show the behaviour of API with empty string in the field "tenant" in header of the request.
We usually share the curl code with the team, so they could replicate the issue.
But got different results, the generated curl code is not what Postman is doing actually.
The generated curl code generates request with field as missing (not included in request).
The Postman app generates a request that includes the field and sets empty value.
So finally you can't use generated code as it is different what Postman is doing actually.
Describe the bug
When a request is made with empty string value in header wrong curl code is generated. It doesn't add ; at the end.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
curl --location --request GET 'localhost/users' --header 'tenant;'
Screenshots
If applicable, add screenshots to help explain your problem. Please make sure the screenshot does not contain any sensitive information such as API keys or access tokens.
App information (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: