You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Base64DecodeExt item in the Reference Manual wiki page provide a link that isn't currently online now. I found a version on Internet Wayback machine, and so I want to update this information. But I don't know how to proppose such change, because the Github pages don't support PRs.
Unfortunately the referred link belongs to an external website that we have no any influence. The other problem is (based on the URI) that page was generated in 2010, so may be it's removed because the owner thought it's too old.
I don't know how correct/polite to put a web.archive.org link into a Wiki page. Any thoughts?
Dear @airween , thanks for your feedback and sorry for the delay.
I'll check with the last version of ModSecurity if the risk indicated on the website is still valid currently. Give me two days.
If the risk exists, I think the important thing here is document on a paragraph the existence of this risk and maybe (or not), bring the user a link with recommendations about secure use of these functions.
Describe the bug
The Base64DecodeExt item in the Reference Manual wiki page provide a link that isn't currently online now. I found a version on Internet Wayback machine, and so I want to update this information. But I don't know how to proppose such change, because the Github pages don't support PRs.
To Reproduce
Following the actual link "blog post on Base64Decoding evasion issues on PHP sites" point to http://blog.spiderlabs.com/2010/04/impedance-mismatch-and-base64.html url, that isn't online.
Expected behavior
The link can point to https://web.archive.org/web/20110713164920/http://blog.spiderlabs.com/2010/04/impedance-mismatch-and-base64.html for example.
The text was updated successfully, but these errors were encountered: