I found a bug where, when sniffing a request that contains a non-standard content-type header (e.g., application/vnd.api+json or others), copying it as a curl command results in the program not adding any content-type header at all, instead of adding the one that was originally in the request. This can cause the server to refuse to accept the request with an unsupported content-type.
Describe the bug
I found a bug where, when sniffing a request that contains a non-standard content-type header (e.g., application/vnd.api+json or others), copying it as a curl command results in the program not adding any content-type header at all, instead of adding the one that was originally in the request. This can cause the server to refuse to accept the request with an unsupported content-type.
To Reproduce Steps to reproduce the behavior:
Information