This is an automated email from the ASF dual-hosted git repository.
wenming pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix.git
The following commit(s) were added to refs/heads/master by this push:
new 9bf0167ed docs: fix usage of incorrect default admin api port (#10391)
9bf0167ed is described below
commit 9bf0167ed0812f33aa3ab5ace69b9b7a97b4fbbc
Author: Abhishek Choudhary <[email protected]>
AuthorDate: Wed Oct 25 12:20:59 2023 +0545
docs: fix usage of incorrect default admin api port (#10391)
---
docs/en/latest/plugins/degraphql.md | 4 ++--
docs/en/latest/plugins/grpc-transcode.md | 8 ++++----
docs/en/latest/tutorials/add-multiple-api-versions.md | 10 +++++-----
docs/zh/latest/plugins/grpc-transcode.md | 8 ++++----
4 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/docs/en/latest/plugins/degraphql.md
b/docs/en/latest/plugins/degraphql.md
index b0eaaf83b..7407a435c 100644
--- a/docs/en/latest/plugins/degraphql.md
+++ b/docs/en/latest/plugins/degraphql.md
@@ -97,7 +97,7 @@ Now we can use RESTful API to query the same data that is
proxy by APISIX.
First, we need to create a route in APISIX, and enable the degreaph plugin on
the route, we need to define the GraphQL query in the plugin's config.
```bash
-curl --location --request PUT 'http://localhost:9080/apisix/admin/routes/1' \
+curl --location --request PUT 'http://localhost:9180/apisix/admin/routes/1' \
--header 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' \
--header 'Content-Type: application/json' \
--data-raw '{
@@ -210,7 +210,7 @@ we can execute it on `http://localhost:8080/playground`,
and get the data as bel
We convert the GraphQL query to JSON string like `"query($name: String!,
$githubAccount: String!) {\n persons(filter: { name: $name, githubAccount:
$githubAccount }) {\n id\n name\n blog\n githubAccount\n talks
{\n id\n title\n }\n }\n}"`, so we create a route like this:
```bash
-curl --location --request PUT 'http://localhost:9080/apisix/admin/routes/1' \
+curl --location --request PUT 'http://localhost:9180/apisix/admin/routes/1' \
--header 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' \
--header 'Content-Type: application/json' \
--data-raw '{
diff --git a/docs/en/latest/plugins/grpc-transcode.md
b/docs/en/latest/plugins/grpc-transcode.md
index 56680946d..9d0fdb46f 100644
--- a/docs/en/latest/plugins/grpc-transcode.md
+++ b/docs/en/latest/plugins/grpc-transcode.md
@@ -238,7 +238,7 @@ If the gRPC service returns an error, there may be a
`grpc-status-details-bin` f
Upload the proto file：
```shell
-curl http://127.0.0.1:9080/apisix/admin/protos/1 \
+curl http://127.0.0.1:9180/apisix/admin/protos/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"content" : "syntax = \"proto3\";
@@ -260,7 +260,7 @@ curl http://127.0.0.1:9080/apisix/admin/protos/1 \
Enable the `grpc-transcode` plugin，and set the option `show_status_in_body` to
`true`：
```shell
-curl http://127.0.0.1:9080/apisix/admin/routes/1 \
+curl http://127.0.0.1:9180/apisix/admin/routes/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"methods": ["GET"],
@@ -308,7 +308,7 @@ Server: APISIX web server
Note that there is an undecoded field in the return body. If you need to
decode the field, you need to add the `message type` of the field in the
uploaded proto file.
```shell
-curl http://127.0.0.1:9080/apisix/admin/protos/1 \
+curl http://127.0.0.1:9180/apisix/admin/protos/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"content" : "syntax = \"proto3\";
@@ -335,7 +335,7 @@ curl http://127.0.0.1:9080/apisix/admin/protos/1 \
Also configure the option `status_detail_type` to `helloworld.ErrorDetail`.
```shell
-curl http://127.0.0.1:9080/apisix/admin/routes/1 \
+curl http://127.0.0.1:9180/apisix/admin/routes/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"methods": ["GET"],
diff --git a/docs/en/latest/tutorials/add-multiple-api-versions.md
b/docs/en/latest/tutorials/add-multiple-api-versions.md
index e48c0c581..f125a542f 100644
--- a/docs/en/latest/tutorials/add-multiple-api-versions.md
+++ b/docs/en/latest/tutorials/add-multiple-api-versions.md
@@ -105,7 +105,7 @@ docker compose up -d
You first need to
[Route](https://apisix.apache.org/docs/apisix/terminology/route/) your HTTP
requests from the gateway to an
[Upstream](https://apisix.apache.org/docs/apisix/terminology/upstream/) (your
API). With APISIX, you can create a route by sending an HTTP request to the
gateway.
```shell
-curl http://apisix:9080/apisix/admin/routes/1 -H 'X-API-KEY: xyz' -X PUT -d '
+curl http://apisix:9180/apisix/admin/routes/1 -H 'X-API-KEY: xyz' -X PUT -d '
{
"name": "Direct Route to Old API",
"methods": ["GET"],
@@ -142,7 +142,7 @@ In the previous step, we created a route that wrapped an
upstream inside its con
Let's create the shared upstream by running below curl cmd:
```shell
-curl http://apisix:9080/apisix/admin/upstreams/1 -H 'X-API-KEY: xyz' -X PUT -d
'
+curl http://apisix:9180/apisix/admin/upstreams/1 -H 'X-API-KEY: xyz' -X PUT -d
'
{
"name": "Old API",
"type": "roundrobin",
@@ -161,7 +161,7 @@ In the scope of this tutorial, we will use _URI path-based
versioning_ because i
Before introducing the new version, we also need to rewrite the query that
comes to the API gateway before forwarding it to the upstream. Because both the
old and new versions should point to the same upstream and the upstream exposes
endpoint `/hello`, not `/v1/hello`. Let’s create a plugin configuration to
rewrite the path:
```shell
-curl http://apisix:9080/apisix/admin/plugin_configs/1 -H 'X-API-KEY: xyz' -X
PUT -d '
+curl http://apisix:9180/apisix/admin/plugin_configs/1 -H 'X-API-KEY: xyz' -X
PUT -d '
{
"plugins": {
"proxy-rewrite": {
@@ -176,7 +176,7 @@ We can now create the second versioned route that
references the existing upstr
> Note that we can create routes for different API versions.
```shell
-curl http://apisix:9080/apisix/admin/routes/2 -H 'X-API-KEY: xyz' -X PUT -d '
+curl http://apisix:9180/apisix/admin/routes/2 -H 'X-API-KEY: xyz' -X PUT -d '
{
"name": "Versioned Route to Old API",
"methods": ["GET"],
@@ -209,7 +209,7 @@ Hello world
We have versioned our API, but our API consumers probably still use the legacy
non-versioned API. We want them to migrate, but we cannot just delete the
legacy route as our users are unaware of it. Fortunately, the `301 HTTP` status
code is our friend: we can let users know that the resource has moved from
`http://apisix.org/hello` to `http://apisix.org/v1/hello`. It requires
configuring the [redirect
plugin](https://apisix.apache.org/docs/apisix/plugins/redirect/) on the initial
route:
```shell
-curl http://apisix:9080/apisix/admin/routes/1 -H 'X-API-KEY: xyz' -X PATCH -d '
+curl http://apisix:9180/apisix/admin/routes/1 -H 'X-API-KEY: xyz' -X PATCH -d '
{
"plugins": {
"redirect": {
diff --git a/docs/zh/latest/plugins/grpc-transcode.md
b/docs/zh/latest/plugins/grpc-transcode.md
index 4c03f4cf9..44445ab85 100644
--- a/docs/zh/latest/plugins/grpc-transcode.md
+++ b/docs/zh/latest/plugins/grpc-transcode.md
@@ -239,7 +239,7 @@ Trailer: grpc-message
上传 proto 文件：
```shell
-curl http://127.0.0.1:9080/apisix/admin/protos/1 \
+curl http://127.0.0.1:9180/apisix/admin/protos/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"content" : "syntax = \"proto3\";
@@ -261,7 +261,7 @@ curl http://127.0.0.1:9080/apisix/admin/protos/1 \
启用 `grpc-transcode` 插件，并设置选项 `show_status_in_body` 为 `true`：
```shell
-curl http://127.0.0.1:9080/apisix/admin/routes/1 \
+curl http://127.0.0.1:9180/apisix/admin/routes/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"methods": ["GET"],
@@ -309,7 +309,7 @@ Server: APISIX web server
注意返回体中还存在未解码的字段，如果需要解码该字段，需要在上传的 proto 文件中加上该字段对应的 `message type`。
```shell
-curl http://127.0.0.1:9080/apisix/admin/protos/1 \
+curl http://127.0.0.1:9180/apisix/admin/protos/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"content" : "syntax = \"proto3\";
@@ -336,7 +336,7 @@ curl http://127.0.0.1:9080/apisix/admin/protos/1 \
同时配置选项 `status_detail_type` 为 `helloworld.ErrorDetail`：
```shell
-curl http://127.0.0.1:9080/apisix/admin/routes/1 \
+curl http://127.0.0.1:9180/apisix/admin/routes/1 \
-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"methods": ["GET"],
