Open wmcsl opened 1 year ago
Thanks for the feedback! Retrieving the values of headers requested fairly frequently - we've added your +1 to this functionality.
We're gathering any bits of feedback about BChecks we can get, so if there's any other functionality you would like to have or you think is missing, then please let us know!
Reopening for better tracking of feature request.
Seconded. I thought I'd write a quick BCheck of people using static nonces in the content security policy. But without a means to access that header's value it doesn't seem possible with BChecks. So :+1: for accessing header content :)
Thanks for the +1!
It is possible to identify specific content using regex matching. However, you will need to be fairly specific with your regular expression to avoid false positives.
I believe a useful feature would be to check the value of a certain header, rather than only checking if the header exists and if the usual values are in the response.
For example, being able to check what the value of the
X-Powered-By
header says would allow authors to provide more relevant guidance for specific text stacks.Another example of where this would be useful would be to move away from the current paradigm of
and "application/json" in {check.response.headers} then
where it's only checking to see if application/json is in any of the headers, not if it's in the Content-Type header.
Example of what I'd like to see:
` detail:
The server announces its underlying technology. {latest.response.headers.X-Powered-By}`and "application/json" in {check.response.headers.Content-Type} then