We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
would there be any interest in having travis actually check the redirect targets from the .htaccess files?
It's not too hard to get the target URIs from the RewriteRules:
find . -name .htaccess -print0 | xargs -0 gsed -r -n 's_^[[:space:]]*RewriteRule[[:space:]]+.*?[[:space:]]+((.*?:)?//.*?)[[:space:]]+.*$_\1_p'
(actually shows quite some non-https URIs btw.)
$[0-9]
$1
Might also be beneficial to have travis submit the URIs and full sites to something like https://web.archive.org ...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
would there be any interest in having travis actually check the redirect targets from the .htaccess files?
It's not too hard to get the target URIs from the RewriteRules:
(actually shows quite some non-https URIs btw.)
$[0-9]
, so they're just static and could just be checked$1
, which just makes the rule shorter, so possible to re-construct the targetMight also be beneficial to have travis submit the URIs and full sites to something like https://web.archive.org ...
The text was updated successfully, but these errors were encountered: