Content-Length is always automatically computed by Firecamp. That's not a problem unless users want to test how their server implementations handle wrong header field sections when e.g. a wrong value of Content-Length is sent.
steps to reproduce
create an API req with a header field Content-Length => send the API req
current behaviour
Custom made Content-Length is not used in requests, it's discarded and the value that Firecamp computes is used instead:
desired behaviour
Allow for overwriting any header fields. In this example, the request would look like:
I guess this is more of a feature than a bug.
Content-Length is always automatically computed by Firecamp. That's not a problem unless users want to test how their server implementations handle wrong header field sections when e.g. a wrong value of Content-Length is sent.
create an API req with a header field Content-Length => send the API req
Custom made Content-Length is not used in requests, it's discarded and the value that Firecamp computes is used instead:
Allow for overwriting any header fields. In this example, the request would look like:
snap, v1.0.0