mandiant/flare-fakenet-ng

More flexibility in HTTP CustomResponse criteria

Open

#148 opened on Oct 2, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (1,626 stars) (359 forks)batch import
featuregood first issue

Description

Software that calls out with varying/random/non-RFC compliant host headers and/or URIs can be difficult to control with the HTTP CustomResponse feature.

It would be nice to be able to enable custom responses unconditionally, or to be able to use wildcards or regex in the host or URI specifications to achieve a similar result.

Contributor guide

Tech stack
python
Domain
backendsecurity
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Python knowledgeHTTP basicsFakeNet NG internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the existing HTTP CustomResponse implementation in FakeNet NG's source code, likely in a module handling HTTP responses. Review how host and URI criteria are currently matched. Consider adding an unconditional mode or implementing wildcard/regex matching. Look for relevant test files to understand the expected behavior.