RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Sherlock] Add verify SSL cert option in requests to bypass WAF

Add a new configuration option to the `data.json` file to support bypassing WAF by disabling SSL certificate verification in specific targets. By setting `verifyCert` to `False`, the `requests` library will send requests with `verify=False`, ignoring SSL certificate verification.

Original Source

@@JackJuly | 0 pts | 12/27/2024

### Description This feature request proposes adding a new configuration option to the `data.json` file to support bypassing WAF by disabling SSL certificate verification in specific targets. By setting `verifyCert` to `False`, the `requests` library will send requests with `verify=False`, ignoring SSL certificate verification. This can enable testing against real IPs or AWS endpoints, effectively bypassing services like Cloudflare WAF. I would like to make a **Pull Request** to implement this feature if the approach is acceptable. ### Implementation Details 1. **Configuration**: - A new setting `verifyCert` has been added to the `data.json` file. - When set to `False`, requests will include `verify=False` to ignore SSL certificate verification. 2. **Functionality**: - This feature allows requests to target real IPs or AWS endpoints without SSL verification. - It is especially useful for testing scenarios where SSL verification is unnecessary or problematic. ###

Discussion

Loading comments...