Unwanted Response Headers
The response contains headers which might leak sensitive information.
Misconfigured HTTP Headers (MHH)
How this template works
The template includes API selection filters that specify the desired response code range (between 200 and 300) and extract the URL from the response using the "urlVar" variable.
The template uses a single request to modify the URL by replacing a placeholder with the extracted URL value. This allows for dynamic URL modification during the execution of the request.
The template includes validation rules to check if the response code falls within the desired range and if any of the specified unwanted response headers are present. The validation checks for the presence of specific header keys using a "contains_either" condition.
Frequently asked questions
What is the purpose of the "Unwanted Response Headers" test in this array
What is the impact of having unwanted response headers in the application
What category and subcategory does the "Unwanted Response Headers" test belong to
What are some examples of unwanted response headers that the test checks for
What are some references provided for further information on unwanted response headers
How does the "Unwanted Response Headers" test modify the request URL