Documenting a much random issue, probably of .NetFramework, that happens once every 3-4 weeks.
We have 3 load-balanced servers in AWS behind ALB. And occassionally, one of the WebAPI servers stops seeing the Content-Type header and infers it to be application/octet-stream.
This is the Good Server that says that the Content-Type application/asdf is invalid.
This is the **Faulty Server** that says the the no Content-Type header was sent, so it is inferring it to be application/octed-stream. Please Note that through Postman, I am sending the Content-Type header as **application/asdf** which is simply getting ignored.
Please note that this has nothing to do with AWS ALB as I have checked this from the localmachine using curl as well. Response is the same.
