fix(otel): support http/https scheme in OTLP endpoint URL#2504
Merged
dgageot merged 1 commit intodocker:mainfrom Apr 24, 2026
Merged
fix(otel): support http/https scheme in OTLP endpoint URL#2504dgageot merged 1 commit intodocker:mainfrom
dgageot merged 1 commit intodocker:mainfrom
Conversation
The OTLP exporter now correctly handles endpoints with explicit http:// or https:// schemes by using WithEndpointURL instead of WithEndpoint. This allows the SDK to determine the transport protocol from the scheme as specified in the OTLP/HTTP specification. Bare host:port endpoints continue to use WithEndpoint with the existing localhost-insecure behavior preserved for backward compatibility.
rumpl
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The OTLP exporter now correctly handles endpoints with explicit
http://orhttps://schemes by usingWithEndpointURLinstead ofWithEndpoint. This allows the SDK to determine the transport protocol from the scheme as specified in the OTLP/HTTP specification.Bare
host:portendpoints continue to useWithEndpointwith the existing localhost-insecure behavior preserved for backward compatibility.