Overriding http host header of gRPC client in golang
It is a common requirement to override the http host header of gRPC client in golang. gRPC is a high-performance, cross-language remote procedure call framework. When using gRPC to communicate, it is sometimes necessary to customize the host header of the http request. PHP editor Xigua will introduce you how to implement this function in golang to better meet your business needs.
Question content
I sent the request over the connection through the gRPC client
conn, err := grpc.Dial("hostname:port",opts...)
From the server side, I see that the host
in http.request is the exact hostname:port
. Then, my nginx server settings are as follows
server { listen port http2; server_name hostname; # ... } server { listen port http2; server_name another_hostname; # ... }
This is a common virtual hosting technology.
No matter which hostname I use in grpc.Dial(xxx:port)
it works fine. However, when I put
md := metadata.New(map[string]string{"host":"another_hostname:port"})
In the grpc context (will be populated in the header of the http2 request). This request will be blocked by nginx and I get
rpc error: code = Internal desc = unexpected HTTP status code received from server: 400 (Bad Request); transport: received unexpected content-type "text/html"
The reason why you need to enter the host name manually is because the host name in grpc.Dial
is fixed. And I can't use a different location to do the reverse proxy because port
is followed by the routing path of the restful api.
If the hostname is fixed and the route is also fixed, are there any other ways to reverse proxy?
(23/09) Update: It turns out that the host header in http2 has been replaced by the :Authority
pseudo header.
Workaround
gRPC uses HTTP/2 and does not use the :host
header, but instead uses the :authority
pseudo-header. The value of this header is determined here: https://github .com/grpc/grpc-go/blob/aa6ce35c792863305e0f42acc27f2c7153275f89/clientconn.go#L1942
TL;PhD
By default, the value used for the :authority
header is the endpoint portion of the user dial target, in the format url://authority/endpoint
.
gRPC-Go also supports a dialup option to override this authority
. See: https://pkg.go.dev/google.golang.org/ grpc#WithAuthority. But also note that this dialing option overrides the ServerName
value used during the TLS handshake.
If you have further questions/concerns, please feel free to contact us via our GitHub repository. Your queries will get better response time there.
The above is the detailed content of Overriding http host header of gRPC client in golang. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

The article discusses the go fmt command in Go programming, which formats code to adhere to official style guidelines. It highlights the importance of go fmt for maintaining code consistency, readability, and reducing style debates. Best practices fo

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...
