-
Notifications
You must be signed in to change notification settings - Fork 30
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
I want to stop forwarding of a specific request path #1237
Comments
🤖 Yes, you can configure GoReplay to forward all requests except for the Here is the command you can use: gor --input-raw :8080 --output-http staging.com --http-disallow-url "/users/.*" This command will forward all requests except those sent to the You can find more information about request filtering in GoReplay in the Request Filtering section of the GoReplay wiki. Also, I can confirm that the current version of GoReplay (v1.3.3) does support the Here is the relevant code: type HTTPModifierConfig struct {
URLNegativeRegexp HTTPURLRegexp `json:"http-disallow-url"`
// other fields...
} This means that when GoReplay is parsing the configuration, it will recognize the I hope this helps! If you have any other questions, feel free to ask. SourcesThis response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
This proposal does not meet the requirements. While control at the path level is indeed possible, it is not feasible at the method level. |
I am currently using goreplay to forward requests to a REST API that provides the following endpoints:
My goal is to forward all requests except for the
[POST] /users/${ID}
endpoint. Unfortunately, the existing options --http-allow-method and --http-allow-url do not fully meet this requirement.Is there any way to meet this requirement?
The text was updated successfully, but these errors were encountered: