[GH-ISSUE #2188] An option to enable TCP KeepAlived for HTTP? #1743

New issue

Closed

opened 2026-05-05 13:07:11 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 13:07:11 -06:00

Owner

Originally created by @LauTrond on GitHub (Jan 13, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2188

The solution you want

Offer an option of type=http, enable TCP KeepAlived for HTTP

Alternatives considered

I found frps make every HTTP request with a single connection, even if both HTTP client and server support Connection: keep-alive
Then I look into vhost/http.go, looks like the vhost disable keep-alived for all requests:

proxy := &ReverseProxy{
    ...
    Transport: &http.Transport{
        ...
        DisableKeepAlives: true

How to implement this function

Application scenarios of this function

We want FRP works faster of HTTP, don't we?

Originally created by @LauTrond on GitHub (Jan 13, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2188  **The solution you want**  Offer an option of type=http, enable TCP KeepAlived for HTTP **Alternatives considered**  I found frps make every HTTP request with a single connection, even if both HTTP client and server support `Connection: keep-alive` Then I look into vhost/http.go, looks like the vhost disable keep-alived for all requests: ``` proxy := &ReverseProxy{ ... Transport: &http.Transport{ ... DisableKeepAlives: true ``` **How to implement this function**  **Application scenarios of this function**  We want FRP works faster of HTTP, don't we?

gitea-mirror

2026-05-05 13:07:11 -06:00

closed this issue
added the
enhancement
label

gitea-mirror commented

2026-05-05 13:07:14 -06:00

Author

Owner

@fatedier commented on GitHub (Jan 13, 2021):

It can't be supported now.

Go http package reuse connections by host. However, frp can route request by host and location(url path). If DisableKeepAlives is false, it will cause mistakes.

Leave this issue open here and we can consider how to achieve it later.

@fatedier commented on GitHub (Jan 13, 2021): It can't be supported now. Go http package reuse connections by host. However, frp can route request by host and location(url path). If `DisableKeepAlives` is false, it will cause mistakes. Leave this issue open here and we can consider how to achieve it later.

gitea-mirror commented

2026-05-05 13:07:15 -06:00

Author

Owner

@LauTrond commented on GitHub (Jan 14, 2021):

It can't be supported now.

Go http package reuse connections by host. However, frp can route request by host and location(url path). If DisableKeepAlives is false, it will cause mistakes.

Leave this issue open here and we can consider how to achieve it later.

Thanks. Sounds like we need multiple *ReverseProxy for multiple destination?

@LauTrond commented on GitHub (Jan 14, 2021): > It can't be supported now. > > Go http package reuse connections by host. However, frp can route request by host and location(url path). If `DisableKeepAlives` is false, it will cause mistakes. > > Leave this issue open here and we can consider how to achieve it later. Thanks. Sounds like we need multiple *ReverseProxy for multiple destination?

gitea-mirror commented

2026-05-05 13:07:16 -06:00

Author

Owner

@fatedier commented on GitHub (Jan 18, 2021):

@LauTrond I have submited a PR https://github.com/fatedier/frp/pull/2199 about to fix this issue, you can try it now and help find if it has bug.

@fatedier commented on GitHub (Jan 18, 2021): @LauTrond I have submited a PR https://github.com/fatedier/frp/pull/2199 about to fix this issue, you can try it now and help find if it has bug.

gitea-mirror referenced this issue

2026-05-05 14:42:16 -06:00

[PR #1743] [CLOSED] typo #4448