hf400159 commented on code in PR #6929: URL: https://github.com/apache/apisix/pull/6929#discussion_r859311912
########## docs/en/latest/getting-started.md: ########## @@ -177,15 +198,13 @@ This response indicates that Apache APISIX is running successfully. } ``` -## Step 2: Create a Route - -[Routes](./architecture-design/route.md) matches the client's requests based on defined rules, loads and executes the corresponding plugins, and forwards the request to the specified upstream. +## Create a Route -From the previous step, we have a running instance of Apache APISIX in Docker. Now let's create a Route. +From the previous step, we have a running instance of APISIX in Docker. Now let's create a Route. -Apache APISIX provides a powerful [Admin API](./admin-api.md) and [APISIX Dashboard](https://github.com/apache/apisix-dashboard). Here, we will use the Admin API to create a Route and connect it to an [Upstream](./architecture-design/upstream.md) service. When a request arrives, Apache APISIX will forward the request to the specified Upstream service. +APISIX provides a powerful [Admin API](./admin-api.md) and [APISIX Dashboard](https://github.com/apache/apisix-dashboard). Here, we will use the Admin API to create a Route and connect it to an [Upstream](./architecture-design/upstream.md) service. When a request arrives, APISIX will forward the request to the specified Upstream service. -We will create a sample configuration for our Route object so that Apache APISIX can forward the request to the corresponding Upstream service. +We will configure the Route so that APISIX can forward the request to the corresponding Upstream service: Review Comment: yes. `:9081` and `:9082` are for the Nginx service. My error is from HTTPbin. So if we use the local Nginx service, this error may not occur. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
