spector - knock sets contentType to application/x-www-form-urlencoded by default when request body missing

[chrisradek]

For some tests that make a post request with an empty request body, the contentType is being set to application/x-www-form-urlencoded.

Example test:

typespec/packages/http-specs/specs/parameters/body-optionality/mockapi.ts

Lines 40 to 45 in bf528cd

	uri: "/parameters/body-optionality/optional-explicit/omit",
	method: "post",
	request: {},
	response: {
	status: 204,
	},

This is due to the behavior of axios where it automatically sets this contentType if one does not exist.

http server emitters should probably be able to handle the case of a missing content-type when the request body is empty, but it would be surprising to see a content-type that it wasn't expecting.

[markcowl]

@chrisradek please confirm if this was fixed

[chrisradek]

@markcowl This is no longer an issue - if a body isn't provided by spector then it omits the content-type header.

There is still a bug here in the http-server-js emitter because it still relies on the content-type being set in this scenario (which it isn't), but I can close this issue since it's specific to spector behavior.

[chrisradek]

#7677 Created for the http-server-js bug