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

-ef parameter only filters at the output level, increasing memory usage #1190

Open
kayra-s4e opened this issue Feb 20, 2025 · 0 comments
Open
Assignees
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@kayra-s4e
Copy link

katana version:

v1.1.2 (latest)

Current Behavior:

When using the -ef parameter to exclude specific file extensions, I can see that they are filtered out in the JSON output. However, when analyzing network traffic with Wireshark, I noticed that requests are still being made to the excluded files.

This suggests that Katana is only filtering these files at the output level, while still storing them in memory. As a result, even with -ef css, CSS files are not included in the output, but they still consume RAM. This leads to excessive memory usage in large-scale crawls.

Expected Behavior:

Katana should completely ignore the specified extensions on the client side and should not send any requests to those files at all.

Steps To Reproduce:

  1. Run the following command:
    katana -u http://testphp.vulnweb.com -ef css -j
  2. Monitor network traffic using Wireshark or Burp Suite.
  3. Notice that requests are still being made to excluded file types (.css).
  4. Observe that CSS files do not appear in the JSON output but still affect RAM usage.

Anything else:

Image

Thank you for your interest

@kayra-s4e kayra-s4e added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Feb 20, 2025
@dogancanbakir dogancanbakir self-assigned this Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

2 participants