Feature Request: 🎯 Add configurable request filtering/visibility controls

[eduardoellery]

📝 Summary

Currently, rep+ automatically filters out certain file types (like .jpg, .png, etc.) from the request list. While this helps reduce noise, it creates a blind spot for security testing scenarios where these "filtered" requests might contain vulnerabilities.

I'd like to request a feature that allows users to:

1. See ALL captured requests (including currently filtered types)
2. Choose which request types to show/hide through configurable filters

✨ Expected Behavior

Option 1: Simple Toggle

• Add a "Show All Requests" toggle that displays everything, including currently filtered file types

Option 2: Advanced Filtering (preferred)

• Provide a filter/preferences panel where users can:
  • Select which file extensions to show/hide (.jpg, .png, .css, .js, etc.)
  • Create custom filter rules
  • Save filter presets for different testing scenarios

Visual mockup concept:

┌─────────────────────────────────┐
│ Filters: [✓] Images             │
│          [✓] Stylesheets         │
│          [✓] Scripts             │
│          [✓] Fonts               │
│          [ ] Show All            │
└─────────────────────────────────┘

💡 Why This Is Helpful

Real-world vulnerability scenario:
I recently encountered a Local File Inclusion (LFI) vulnerability that went unnoticed because the application was loading image filenames via GET parameters:

GET /page.php?image=../../../../etc/passwd.jpg

Because rep+ filtered out .jpg requests, this suspicious request never appeared in my request list, and I only discovered the vulnerability much later through other testing methods.

Other use cases:

• Parameter tampering in image/media requests
• Path traversal vulnerabilities in asset loading
• IDOR issues in file download endpoints
• Cache poisoning via static resource URLs
• Authentication bypass in image/document serving logic

Being able to see all requests, regardless of file type, is crucial for comprehensive security testing. Different testing scenarios require different levels of visibility, and having configurable filters would make rep+ much more flexible for bug bounty hunters and penetration testers.

🔧 Implementation Notes

A simple approach could be:

1. Remove/modify the current hardcoded file extension filters
2. Add user-configurable filter checkboxes in the Settings/Filters UI
3. Store filter preferences in local storage
4. Apply filters client-side when rendering the request list

---

Thanks for building such an awesome tool! This feature would make rep+ even more powerful for security testing workflows. 🙏