server.ServeHTTP Experimental Status about grpc-go HOT 9 OPEN

Yes, it is marked as experimental currently. I will confirm with the team if can remove experimental status

from grpc-go.

There are no plans to stabilize the functionality. gRPC's HTTP/2 server provides more features than the Go HTTP server and we haven't yet heard any critical use cases that require the Go HTTP server, so it's hard to justify spending time improving it.

from grpc-go.

@ekky-kharismadhany do you have any specific use case that's relevant here?

from grpc-go.

Hi, sorry for the late reply

I currently working on some application that use grpc-gateway project. On those projects, my organization uses same port to serve RESTful API and gRPC.

The current implementation is using a third-party library which currently does not have any update for the last 3 years. So, I'm searching a method to handle this issue and found that server.ServeHTTP can be used to solve my organization issue.

That being said, do you have any recommendation or experience on how an application can serve both RESTful and gRPC at the same port?

Thank you

from grpc-go.

Another way I used that API was by wrapping it with an HTTP middleware it could serve also grpc-web requests. It required h2 also for grpc-web requests, but it worked well for unary and server streaming RPCs.

There are some implementations that offer also grpc-web, it might be considered.

from grpc-go.

Hi @isgj , I also use h2c for my proof-of-concept code. It works well.

	server := grpc.NewServer(opts...)
	reflection.Register(server)
	echo_rpc.RegisterEchoServerServer(server, initServer())
	logger.Info("server started", "host", host)
	multiServer := http.Server{
		Handler: h2c.NewHandler(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
			if r.ProtoMajor == 2 && r.Header.Get("content-type") == "application/grpc" {
				server.ServeHTTP(w, r)
			} else {
				mux.ServeHTTP(w, r)
			}
		}), &http2.Server{}),
	}
	if err := multiServer.Serve(listener); err != nil {
		panic(err.Error())
	}

from grpc-go.

Better approach would be to have a proxy or custom middleware for routing traffic accordingly. Alternatively, you can consider libraries like cmux to multiplex connections based on their payload

from grpc-go.

Hi @purnesh42H

cmux is the third-party project I referred to earlier in this issue. I'm looking for an alternative to cmux. But your approach on using proxy or a custom middleware is interesting. Could you elaborate those approaches, please?

Thank you

from grpc-go.