Skip to content

[1.18] service-invocation: document hop-by-hop header stripping in v1.18 #5172

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.

Sign up for GitHub

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

Open
JoshVanL wants to merge 3 commits into
base: v1.18
Choose a base branch
from
+6 −0
Open

[1.18] service-invocation: document hop-by-hop header stripping in v1.18 #5172

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c94ce49
service-invocation: document hop-by-hop header stripping in v1.18
JoshVanL May 19, 2026
0c674fc
Update daprdocs/content/en/developing-applications/building-blocks/se…
marcduiker May 20, 2026
51aa319
Merge branch 'v1.18' into joshvanl/v1.18-svc-invoke-hop-by-hop
marcduiker May 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions ...-applications/building-blocks/service-invocation/service-invocation-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,12 @@ Self-hosted machines can use the mDNS name resolution component. As an alternati

The Consul name resolution component is particularly suited to multi-machine deployments and can be used in any hosting environment, including Kubernetes, multiple VMs, or self-hosted.

### Hop-by-hop header stripping

When proxying HTTP service invocation, Dapr removes the standard hop-by-hop headers defined in [RFC 7230 Section 6.1](https://datatracker.ietf.org/doc/html/rfc7230#section-6.1) before forwarding the request to the upstream application or [HTTPEndpoint]({{% ref "httpendpoints-schema.md" %}}), and again before forwarding the upstream's response back to the caller. These headers are: `Connection`, `Keep-Alive`, `Proxy-Connection`, `Transfer-Encoding`, `Upgrade`, `HTTP2-Settings`, `TE`, `Trailer`, and `Proxy-Authorization`.

End-to-end headers (`Accept`, `Authorization`, `Content-Type`, custom `X-*` headers, etc.) are not affected and continue to be forwarded unchanged.

### Streaming for HTTP service invocation

You can handle data as a stream in HTTP service invocation. This can offer improvements in performance and memory utilization when using Dapr to invoke another service using HTTP with large request or response bodies.
Expand Down
Loading