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

Adding pagination to the API #106

Open
JoshuaMart opened this issue Aug 19, 2022 · 1 comment
Open

Adding pagination to the API #106

JoshuaMart opened this issue Aug 19, 2022 · 1 comment
Assignees
Labels
Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@JoshuaMart
Copy link

Hi,
I could notice that in the case of important scopes, the use of Chaos in Amass simply makes the tool crash due to an excessive consumption of memory.

I think this is partly due to the lack of pagination. In general this would be a useful addition. For example, with the domain `army.mil, a 65MB response for 2 493 133 results is returned (not even 1% of the results seem to be alive).
So in general, even with other tools there are performance issues.

So I think it would be nice to have a pagination system either fixed or with a limit to return a certain number of results.

Regards

@JoshuaMart JoshuaMart added the Type: Enhancement Most issues will probably ask for additions or changes. label Aug 19, 2022
@serialfuzzer
Copy link

Same issue here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

No branches or pull requests

3 participants