API Testing Challenge 22 - How To - Post todos 415 status unsupported content type
API Testing Challenge 22 - How To - Post todos 415 status unsupported content type
How to complete the challenge POST /todos (415) to send a POST request to try and create a todo item but with unsupported content type.
Issue a POST request on the /todos end point with an unsupported content type to generate a 415 status code
For this challenge we issue a request with a content-type which is unsupported.
- POST request means we will send information in the body of the message - e.g. POST /todos sends to the todos endpoint - unsupported content type means that we will set content-type to something unknown eg. bob - add the X-CHALLENGER header to track progress - we know it has been rejected when we receive a 415 response - the body of the response should contain the full details of the error message
For a write up of this solution, check out the blog post: