litespeedtech / litespeedtech/openlitespeed
http2 in upstream proxy connections
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 233
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
I have a backend server 127.0.0.1:8000 that supports http2 only (because it uses nghttp2 library), no http 1.1, no connection Upgrade command.
I am trying to configure my OpenLiteSpeed reverse proxy to my backend server using the following in extprocessor {..}
**address h2://127.0.0.1:8000**
This does not work. If I disable SSL in my backend server and try the following
**address h2c://127.0.0.1:8000**
also does not work.
How to use http2 in upstream proxy connections? Alternatively, how to connect to backend **gRPC** server?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by locating the extprocessor address parsing and upstream proxy protocol handling, then trace how h2 and h2c addresses are processed. Done means establishing whether HTTP/2 or gRPC upstream connections are supported and documenting or testing the resulting configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, grpc
- Domain
- backend-api-design, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100