Skip to content
New issue

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

travis actually check redirect targets from .htaccess? #338

Open
joernhees opened this issue Apr 16, 2016 · 0 comments
Open

travis actually check redirect targets from .htaccess? #338

joernhees opened this issue Apr 16, 2016 · 0 comments

Comments

@joernhees
Copy link
Contributor

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.)

  • Very many of them don't contain a $[0-9], so they're just static and could just be checked
  • many of the rules contain a "static" $1, which just makes the rule shorter, so possible to re-construct the target
  • for those which don't, we could at least check if the domain resolves and something answers...

Might also be beneficial to have travis submit the URIs and full sites to something like https://web.archive.org ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant