runner

History

Jason Song 8996b9b0e4 Disable HTTP/2 (#4 ) We use [connect-go](https://github.com/bufbuild/connect-go) instead of [grpc-go](https://github.com/grpc/grpc-go) because connect-go support HTTP/1.1, that means we can mount the gRPC api on the Gitea server without change the protocol. So it doesn't make sense that make the runner support both HTTP/1.1 and HTTP/2, and [upgrade the protocol used on Gitea]( `ae018b6b48/modules/graceful/server_http.go (L23)`) to support HTTP/2 and h2c. Although it works right now, I believe there'll be lots of problems when the Gitea server is behind a reverse proxy. So let's KISS, we don't touch the http protocol of Gitea, and disable HTTP/2 for runner. And we would support HTTP/2 in the future if we really need it. Co-authored-by: Jason Song <i@wolfogre.com> Reviewed-on: https://gitea.com/gitea/act_runner/pulls/4	2022-11-29 10:35:59 +08:00
..
client.go	feat: use specified labels	2022-11-24 15:38:21 +08:00
http.go	Disable HTTP/2 (#4 )	2022-11-29 10:35:59 +08:00

Jason Song 8996b9b0e4 Disable HTTP/2 (#4 )

We use [connect-go](https://github.com/bufbuild/connect-go) instead of [grpc-go](https://github.com/grpc/grpc-go) because connect-go support HTTP/1.1, that means we can mount the gRPC api on the Gitea server without change the protocol.

So it doesn't make sense that make the runner support both HTTP/1.1 and HTTP/2, and [upgrade the protocol used on Gitea](
ae018b6b48/modules/graceful/server_http.go (L23)) to support HTTP/2 and h2c. Although it works right now, I believe there'll be lots of problems when the Gitea server is behind a reverse proxy.

So let's KISS, we don't touch the http protocol of Gitea, and disable HTTP/2 for runner. And we would support HTTP/2 in the future if we really need it.

Co-authored-by: Jason Song <i@wolfogre.com>
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/4

2022-11-29 10:35:59 +08:00

client.go feat: use specified labels 2022-11-24 15:38:21 +08:00

http.go Disable HTTP/2 (#4 ) 2022-11-29 10:35:59 +08:00