You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some queries, there will be a large amount of data returned. For example, when doing a cvefor query, a user may not want the full CVE entry for things -- but rather may benefit from a smaller subset of fields. This is important to make the query more efficient in terms of data transfer on both sides.
For example, when GETing https://cve.circl.lu/api/cvefor/cpe:2.3:a:openssl:openssl:0.9.8a:*:*:*:*:*:*:*, there is a large amount of Nessus data coming back. In some cases (such as mine), there is no need for this data at all. Furthermore, if one runs entirely on CPE v2.3, they may not need the CPE v2.2 fields.
This would bring the API in line with common practices to make it possible request the fields desired to be returned.
The text was updated successfully, but these errors were encountered:
I'd like to second that. Would be nice if there is a way to request only the last 5 items for example, when submitting a request to /search/vendor/product. Or alternatively, if there would be a way to pass vendor and product when requesting from /last.
For some queries, there will be a large amount of data returned. For example, when doing a cvefor query, a user may not want the full CVE entry for things -- but rather may benefit from a smaller subset of fields. This is important to make the query more efficient in terms of data transfer on both sides.
For example, when GETing
https://cve.circl.lu/api/cvefor/cpe:2.3:a:openssl:openssl:0.9.8a:*:*:*:*:*:*:*
, there is a large amount of Nessus data coming back. In some cases (such as mine), there is no need for this data at all. Furthermore, if one runs entirely on CPE v2.3, they may not need the CPE v2.2 fields.This would bring the API in line with common practices to make it possible request the fields desired to be returned.
The text was updated successfully, but these errors were encountered: