Hi there,
I work with someone who has had their Apache 2 web server tested for PCI compliance, and one of the issues they had flagged up was, "Because the scanner was able to find a specific forbidden directory, it should remain forbidden even if some hex encoding is being input."
The example I have is, theirwebsite.com/any-folder/ gives a 403 directory forbidden error, whilst theirwebsite.com/any-folder/%3fD=A gives a 404 file not found error.
They say that even when adding the hex encoding, it should still be giving a 403 error, rather than the 404 error.
I'm not even sure I understand what the issue is here, but assuming this is an issue and those who know more than me understand it, do you have any ideas for how to remedy this behaviour?
Thanks,
Stephen