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

Allow exclusion of URL's from crawler #1019

Closed
tohmjudson-ms opened this issue Jan 26, 2022 · 4 comments
Closed

Allow exclusion of URL's from crawler #1019

tohmjudson-ms opened this issue Jan 26, 2022 · 4 comments
Labels
feature request resolution: out of scope This issue has been identified as out of scope for this project.

Comments

@tohmjudson-ms
Copy link

Problem

When using the Accessibility Insights Azure DevOps Task, the pipeline allows for the use of discovery patterns. However, this appears to be limited to adding URL and not excluding them.

Ask

I would like to see an additional parameter to exclude URLs via regex (or other options) in the same manner as the discovery pattern

Examples:

Exclude url’s that include query parameters (everything after /?)
Exclude url’s that are in the domain but fall into a specific subdomain or path (like example.com/blog/....)
I am sure there are other ideas as well :)

@ghost ghost added the status: new This issue is new and requires triage by DRI. label Jan 26, 2022
@ghost ghost assigned DaveTryon Jan 26, 2022
@DaveTryon DaveTryon added status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. and removed status: new This issue is new and requires triage by DRI. labels Jan 26, 2022
@ghost ghost assigned asksep Jan 26, 2022
@ghost
Copy link

ghost commented Jan 26, 2022

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

@DaveTryon DaveTryon assigned DaveTryon and asksep and unassigned asksep and DaveTryon Jan 26, 2022
@ferBonnin ferBonnin added help wanted Extra attention is needed status: ready for work This issue is ready to be worked on. labels Feb 7, 2022
@ghost ghost removed the status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. label Feb 7, 2022
@ferBonnin
Copy link
Contributor

triaged with the team. Agreed to add this to our backlog. Some additional notes

  • we should capture the command line (both allow and reject) somewhere so users know how these results were found.
  • marking this as help wanted in case someone wants to take this on sooner

@brocktaylor7
Copy link
Contributor

The implementation for this will need to happen on the Accessibility Insights Service as the crawling logic and inputs all pass through to a library we consume from that repo. I've filed a feature request on that repo to give broader visibility. You can find the new issue here: microsoft/accessibility-insights-service#2208

@asksep asksep closed this as completed Aug 15, 2022
@ferBonnin ferBonnin added the resolution: out of scope This issue has been identified as out of scope for this project. label Oct 31, 2022
@ghost
Copy link

ghost commented Oct 31, 2022

This issue has been marked as being beyond the support scope of Accessibility Insights. It will now be closed automatically for house-keeping purposes.

@ghost ghost removed the status: ready for work This issue is ready to be worked on. label Oct 31, 2022
@DaveTryon DaveTryon removed the help wanted Extra attention is needed label Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request resolution: out of scope This issue has been identified as out of scope for this project.
Projects
None yet
Development

No branches or pull requests

5 participants