3 ms·
Some FAQs: - This only affects rewrite conditions which literally start with “RewriteCond expr”; this is a special form that causes the condition pattern to be
by nneonneo 1y ago
Some FAQs:
- This only affects rewrite conditions which literally start with “RewriteCond expr”; this is a special form that causes the condition pattern to be treated as an Apache expression. See the documentation on that feature here: https://httpd.apache.org/docs/trunk/mod/mod_rewrite.html#:~:text=RewriteCond%20expr,-%22!%20%25%7BHTTP_REFERER%7D%20%2Dstrmatch%20'*://%25%7BHTTP_HOST https://httpd.apache.org/docs/trunk/mod/mod_rewrite.html#:~:...
- Yes, there are tests. They’re stored in a separate repository. Here are the regression tests added for this bug: https://github.com/apache/httpd-tests/commit/48a85e34051959c5fa3ee6e0deb35a9acd4e8d59 https://github.com/apache/httpd-tests/commit/48a85e34051959c.... As for why testing didn’t find this bug in the first place, you can see that they have tests for RewriteCond, but just not for expression conditions, likely due to the relative rarity of that subfeature.
- ameliaquining 1y agoThis still suggests that nobody's checking for adequate test coverage, if a feature that has its own dedicated syntax didn't have any. (Also, I can't find any documentation on how to measure coverage while running the test suite, which suggests that nobody is doing this routinely.) But admittedly this is a lesser sin than not having tests at all.
- philipwhiuk 1y agoIf the tests aren't run on check-in you may as well not have them.