Is it possible to disable the Connect protocol?

[JPFrancoia]

Hi,
First of, Connect is amazing. It fixes most of the annoying things with gRPC. It makes debugging super easy with the Connect protocol and I don't need to deploy an Envoy proxy to support grpc-web.

Hopefully this will be a quick question. I'm preparing to rollout my backend, implemented with Connect. The backend needs to support the gRPC and gRPC-web protocols (these are the protocols used by my clients). However I do not want the Connect protocol to be enabled once the backend is deployed. It's very practical for development, but once live I don't want it enabled. Is there a way to disable it?

I could write an interceptor to reject requests with the Connect-Protocol-Version header, but I was wondering if there is a better way.

Cheers

[emcfarlane]

It's currently not an option that is supported. As a workaround for now you may inspect the content type to classify the request as a grpc/grpcWeb request and return a 415 Unsupported Media Type status otherwise. Here is an example in HTTP middleware:

func grpcOnlyMiddleware(next http.Handler) http.Handler {
	return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		if !strings.HasPrefix(r.Header.Get("Content-Type"), "application/grpc") {
			w.WriteHeader(http.StatusUnsupportedMediaType)
			return
		}
		next.ServeHTTP(w, r)
	})
}

[JPFrancoia]

Perfect, works like a charm, thank you.