-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/httpcheck] Add configuration option to prevent following redirections #34623
Labels
Comments
rogercoll
added
enhancement
New feature or request
needs triage
New item requiring triage
labels
Aug 12, 2024
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Sounds good to me. Probably requires to be added to confighttp. |
+1 to add the config option to confihttp ( |
This was referenced Aug 27, 2024
This was referenced Sep 10, 2024
This was referenced Sep 24, 2024
Hi, |
Hi @AwsmAshraf , Yes, there is this ongoing PR: open-telemetry/opentelemetry-collector#10877 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/httpcheck
Is your feature request related to a problem? Please describe.
An HTTP endpoint can return either 307 or 308 as status code when it has been redirected. Let's say I want to monitor a temporal redirection (307) and act upon changes (e.g. end of redirection → 2xx).
For example, the
http://wikipedia.com
endpoint is redirected to thehttps://wikipedia.com
but I don't want to ensure its reachability but its redirection. Receiver config:The default http client seems to be following redirects, thus getting a 2xx instead:
Describe the solution you'd like
A config option to define the maximum number of redirects or completely disable them by default.
For example, Elastic uses the max_redirects configuration options which defaults to 0 (so no redirects are followed, but the status of the redirect is reported)
Describe alternatives you've considered
Adding the configuration option in the confighttp
Additional context
No response
The text was updated successfully, but these errors were encountered: