Appropriate Content-Type header not set on import of postman collection with Form URL Encoded body

[amargulies]

Expected Behavior

When importing the attached exported collection from postman, I expect that upon running the subsequent request, I would get

--header 'Content-Type: application/x-www-form-urlencoded'

in the request.

New Collection.postman_collection.json

Actual Behavior

No Header gets generated / sent out. If I change the request body to something else then change it back to Form URL Encoded only then does the header get generated / sent.

Reproduction Steps

1. Import the attached postman collection
   New Collection.postman_collection.json
2. In the "New Collection" folder, select "New Request"
3. Click on the drop-down next to "Send" and select "Show CURL code, etc"
4. Note the lack of --header 'Content-Type: application/x-www-form-urlencoded' !!!!
5. Change the request body type from Form URL Encoded to something else
6. Change the request body type back to Form URL Encoded
7. Click on the drop-down next to "Send" and select "Show CURL code, etc"
8. Marvel at the sudden appearance of --header 'Content-Type: application/x-www-form-urlencoded' !!!

Is there an existing issue for this?

• I have searched the issue tracker for this problem.

Additional Information

This does not seem to be OS dependent behavior. I initially saw this on my work mac and could reproduce on my personal Windows 10 desktop

Insomnium Version

0.2.3-a

What operating system are you using?

Windows

Operating System Version

Edition Windows 10 Pro Version 22H2 Installed on ‎3/‎5/‎2022 OS build 19045.4046 Experience Windows Feature Experience Pack 1000.19053.1000.0

Installation method

Download exe from releases on github

Last Known Working Insomnium version

No response