-
Notifications
You must be signed in to change notification settings - Fork 178
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
Create shorter redirect link format for vulnerabilities #930
Comments
The number of times I've tried and failed to use just osv.dev/id, could we support that for maximum URL brevity? Feels more intuitive. |
Yeah that's certainly another possibility, just wonder if it creates any complexities in the future since it introduces potential routing clashes with other top level OSV.dev pages. |
Yes, there's a (small, IMO) risk, given all of the IDs should be fairly unambiguously regex-able... |
https://osv.dev/VULN-ID would redirect to https://osv.dev/vulnerability/VULN-ID, if VULN-ID exists. Fixes #930.
https://osv.dev/VULN-ID would redirect to https://osv.dev/vulnerability/VULN-ID, if VULN-ID exists. Fixes #930.
https://osv.dev/VULN-ID would redirect to https://osv.dev/vulnerability/VULN-ID, if VULN-ID exists. Fixes #930.
One observation: this doesn't work for aliases, and I wonder whether it could/should? In my opinion it would be much more delightful for our users if it did... e.g. I can go the long way around to search for CVE-2013-5823, which turns out to be an alias for GHSA-8gwc-x7mg-7p7p, but I can't go to osv.dev/CVE-2013-5823 successfully. |
e.g.
https://osv.dev/v/PYSEC-foo
should redirect to the fullhttps://osv.dev/vulnerability/PYSEC-foo
.This can help with osv-scanner's human readable output, where horizontal space is a premium.
The text was updated successfully, but these errors were encountered: