Support tracking targets by full URL
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 15
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 22
Description
We would like to be able to point Tracker at a full URL when performing its scans, instead of just a domain name. The requirement behind this is the use of a managed service, which when used in certain scenarios only grants us control of the ciphers/protocols/headers at specific paths, and not at the root URL.
For example, with Azure APIM (a managed API gateway), we can control the ciphers + protocols on the gateway itself (hxxps://apim.tbs/) so as to align with ITSP.40.062.
However for things such as HSTS headers, we can only control those on a per-API level (via "APIM API policies"). Those individual APIs would only be accessible to Tracker by a path such as hxxps://apim.tbs/pingApi/ping.
I fear this may have cascading effects on your data model, but it would be nice to have.
Contributor guide
Assessment
This issue has not been assessed yet.