hnlq715 commented on a change in pull request #3547:
URL: https://github.com/apache/apisix/pull/3547#discussion_r571811074



##########
File path: conf/config.yaml
##########
@@ -31,6 +31,12 @@
 #
 # If the configured environment variable can't be found, an error will be 
thrown.
 apisix:
+  node_listen:
+    - port: 9080                     # APISIX listening port
+      enable_http2: false            # Disable to support HTTP proxy, nginx 
currently do not support HTTP and HTTP/2 with plaintext on the same port
+                                     # Details can be found in 
https://trac.nginx.org/nginx/ticket/816
+    - port: 9081                     # APISIX listening port for HTTP/2 with 
plaintext

Review comment:
       done

##########
File path: doc/grpc-proxy.md
##########
@@ -36,7 +36,8 @@ gRPC client -> APISIX -> gRPC/gRPCS server
 Here's an example, to proxying gRPC service by specified route:
 
 * attention: the `scheme` of the route's upstream must be `grpc` or `grpcs`.
-* attention: APISIX use TLS‑encrypted HTTP/2 to expose gRPC service, so need 
to [config SSL certificate](https.md)
+* attention: APISIX use TLS‑encrypted HTTP/2 to expose gRPC service (default 
port 9443), so need to [config SSL certificate](https.md)
+* attention: APISIX also support to expose gRPC service with plaintext HTTP/2 
(default port 9081), which do not need to config SSL certificate, usually used 
to proxy gRPC service in intranet environment

Review comment:
       done

##########
File path: conf/config.yaml
##########
@@ -31,6 +31,12 @@
 #
 # If the configured environment variable can't be found, an error will be 
thrown.
 apisix:
+  node_listen:
+    - port: 9080                     # APISIX listening port

Review comment:
       done




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to