Filter Based on Status Response
ThunderSon opened this issue · comments
Hello!
Is there a possibility to add the option to filter based on the response status? In some projects, I receive a status of 0, or 403, while they are functioning normally (So mainly related to how they're being responsive to the tool).
Let me know if I can help as well.
http 403 is forbidden. Maybe, that URLs should be included as URL pattern?
In my case, I would like to filter out HTTP 429 Too Many Requests. This happens when I'm checking links to github.com repositories using github workflows
We have the same exact use case and issue as @koppor with a GitHub Actions workflow checking links against github.com, where it can occasionally return a 429 status code for random links. In our case we would be okay to ignore those although ideally it would retry.
Example GitHub Actions run: https://github.com/terraform-providers/terraform-provider-aws/pull/13655/checks?check_run_id=747512585
FILE: docs/MAINTAINING.md
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/provider → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/question → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/regression → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/reinvent → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/stale → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/technical-debt → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/tests → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/thinking → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/upstream-terraform → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/upstream → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/waiting-response → Status: 429
85 links checked.
ERROR: 11 dead links found!
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/provider → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/question → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/regression → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/reinvent → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/stale → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/technical-debt → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/tests → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/thinking → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/upstream-terraform → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/upstream → Status: 429
[✖] https://github.com/terraform-providers/terraform-provider-aws/labels/waiting-response → Status: 429
I pushed a PR for this http 429 issue #106
Hopefully it will be merged.