[GitHub] [apisix-dashboard] Baoyuantop commented on issue #2673: Source-based installation fails

[GitBox]

Baoyuantop commented on issue #2673:
URL: 
https://github.com/apache/apisix-dashboard/issues/2673#issuecomment-1398034281

   Hi @Cheol-Soon-Choi, if there are still problems, you can reopen


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-dashboard] Baoyuantop closed issue #2673: Source-based installation fails

[GitBox]

Baoyuantop closed issue #2673: Source-based installation fails
URL: https://github.com/apache/apisix-dashboard/issues/2673


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-dashboard] Baoyuantop commented on issue #2687: bug: dashboard should not support '!' in vars.

[GitBox]

Baoyuantop commented on issue #2687:
URL: 
https://github.com/apache/apisix-dashboard/issues/2687#issuecomment-1398030408

   Hi @840963657, can you help with the specific steps to create this route 
using the dashboard? Also, you can try the latest version of the dashboard.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1398028051

   Perhaps you have other routes that conflict with this route? If you 
configure a /* route, it is possible that the route will override the match of 
the /food/* route. Please checkout


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1398026429

   I really don't know why this can't work for your local system.
   This is my step.
   First, create an upstream.
   ```json
   {
 "nodes": [
   {
 "host": "httpbin.org",
 "port": 80,
 "weight": 1
   }
 ],
 "timeout": {
   "connect": 6,
   "send": 6,
   "read": 6
 },
 "type": "roundrobin",
 "scheme": "http",
 "pass_host": "pass",
 "name": "httpbin",
 "keepalive_pool": {
   "idle_timeout": 60,
   "requests": 1000,
   "size": 320
 }
   }
   ```
   I'm using `httpbin.org` for the test.
   https://user-images.githubusercontent.com/11229089/213642473-53840dbd-b85f-414e-9004-54f236718e40.png";>
   Now I get an upstream id: 444043510262268609
   
   Secondly, open a `Raw data editor` in route config page.
   https://user-images.githubusercontent.com/11229089/213642851-a2ecf3bd-af5d-4bf3-ad5e-11d53bc9293f.png";>
   
   Then, paste all configs you are posting previously. Only change upstream id 
to my upstream id
   https://user-images.githubusercontent.com/11229089/213642943-87dd06a8-34b4-48e2-9e42-f1275cd5ccfe.png";>
   
   Then, create this route successfully.
   https://user-images.githubusercontent.com/11229089/213643215-80951ab0-2c5f-4edc-a2d8-011bf4479cce.png";>
   
   Finally, I access from curl
   https://user-images.githubusercontent.com/11229089/213643475-a98eddd4-50db-44e3-950d-7e3ebb8880a9.png";>
   
   https://user-images.githubusercontent.com/11229089/213643552-86877b07-c82c-4f59-90f4-f38d1bca2959.png";>
   
   You can see, I access using `/food/get`, and APISIX has rewritten this URL 
to `/get` success.
   So when I access `http://localhost:9080/food/get` APISIX will access 
`http://httpbin.org/get` and return what their return.
   This means everything works correctly.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-dashboard] Baoyuantop commented on issue #2691: dashboard can not start when a custom discovery plugins enabled

[GitBox]

Baoyuantop commented on issue #2691:
URL: 
https://github.com/apache/apisix-dashboard/issues/2691#issuecomment-1398026131

   Hi @jagerzhang, have you tried to synchronize schema information? You can 
refer here 
https://apisix.apache.org/docs/dashboard/FAQ/#4-after-modifying-the-plugin-schema-or-creating-a-custom-plugin-in-apache-apisix-why-cant-i-find-it-on-the-dashboard


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-dashboard] codecov-commenter commented on pull request #2718: fix: plugin configuration lost in editor

[GitBox]

codecov-commenter commented on PR #2718:
URL: 
https://github.com/apache/apisix-dashboard/pull/2718#issuecomment-1398023204

   # 
[Codecov](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 Report
   > Merging 
[#2718](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (4e6c304) into 
[master](https://codecov.io/gh/apache/apisix-dashboard/commit/7b8d9c5b30a8eae2ca038b99cf2a3c36cdca2ddc?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (7b8d9c5) will **increase** coverage by `12.96%`.
   > The diff coverage is `100.00%`.
   
   ```diff
   @@ Coverage Diff @@
   ##   master#2718   +/-   ##
   ===
   + Coverage   55.01%   67.98%   +12.96% 
   ===
 Files 104   39   -65 
 Lines2983 1040 -1943 
 Branches  743  268  -475 
   ===
   - Hits 1641  707  -934 
   + Misses   1342  333 -1009 
   ```
   
   | Flag | Coverage Δ | |
   |---|---|---|
   | frontend-e2e-test | `67.98% <100.00%> (+12.96%)` | :arrow_up: |
   
   Flags with carried forward coverage won't be shown. [Click 
here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#carryforward-flags-in-the-pull-request-comment)
 to find out more.
   
   | [Impacted 
Files](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 | Coverage Δ | |
   |---|---|---|
   | 
[web/src/components/Plugin/PluginDetail.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9jb21wb25lbnRzL1BsdWdpbi9QbHVnaW5EZXRhaWwudHN4)
 | `64.48% <100.00%> (-10.93%)` | :arrow_down: |
   | 
[web/src/components/PanelSection/index.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9jb21wb25lbnRzL1BhbmVsU2VjdGlvbi9pbmRleC50c3g=)
 | `75.00% <0.00%> (-25.00%)` | :arrow_down: |
   | 
[web/src/helpers.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9oZWxwZXJzLnRzeA==)
 | `19.67% <0.00%> (-19.68%)` | :arrow_down: |
   | 
[web/src/components/ActionBar/ActionBar.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9jb21wb25lbnRzL0FjdGlvbkJhci9BY3Rpb25CYXIudHN4)
 | `69.23% <0.00%> (-7.70%)` | :arrow_down: |
   | 
[web/src/components/Plugin/PluginPage.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9jb21wb25lbnRzL1BsdWdpbi9QbHVnaW5QYWdlLnRzeA==)
 | `82.00% <0.00%> (-5.00%)` | :arrow_down: |
   | 
[web/src/components/Plugin/UI/plugin.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9jb21wb25lbnRzL1BsdWdpbi9VSS9wbHVnaW4udHN4)
 | `87.50% <0.00%> (-4.17%)` | :arrow_down: |
   | 
[web/src/app.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9hcHAudHN4)
 | `87.87% <0.00%> (-3.04%)` | :arrow_down: |
   | 
[web/src/components/Plugin/UI/api-breaker.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation#diff-d2ViL3NyYy9jb21wb25lbnRzL1BsdWdpbi9VSS9hcGktYnJlYWtlci50c3g=)
 | `69.23% <0.00%> (ø)` | |
   | 
[...mponents/Upstream/components/active-check/Port.tsx](https://codecov.io/gh/apache/apisix-dashboard/pull/2718?src=pr&el=tree&utm_medium=referral&utm_source=github&ut

[GitHub] [apisix-dashboard] Baoyuantop commented on issue #2707: ip限制插件配置UI展示异常

[GitBox]

Baoyuantop commented on issue #2707:
URL: 
https://github.com/apache/apisix-dashboard/issues/2707#issuecomment-1398021204

   Looks similar to https://github.com/apache/apisix-dashboard/issues/2696


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-dashboard] Baoyuantop opened a new pull request, #2718: fix: plugin configuration lost in editor

[GitBox]

Baoyuantop opened a new pull request, #2718:
URL: https://github.com/apache/apisix-dashboard/pull/2718

   Please answer these questions before submitting a pull request, **or your PR 
will get closed**.
   
   **Why submit this pull request?**
   
   - [x] Bugfix
   - [ ] New feature provided
   - [ ] Improve performance
   - [ ] Backport patches
   
   **What changes will this PR take into?**
   
   Please update this section with detailed description.
   
   **Related issues**
   
   fix/resolve https://github.com/apache/apisix-dashboard/issues/2696
   
   **Checklist:**
   
   - [x] Did you explain what problem does this PR solve? Or what new features 
have been added?
   - [x] Have you added corresponding test cases?
   - [ ] Have you modified the corresponding document?
   - [ ] Is this PR backward compatible? If it is not backward compatible, 
please discuss on the mailing list first
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] xiaoxuanzi opened a new pull request, #8716: feat(clickhouse-logger): unify endpoints into one schema

[GitBox]

xiaoxuanzi opened a new pull request, #8716:
URL: https://github.com/apache/apisix/pull/8716

   ### Description
   
   clickhouse-logger: unify endpoints into one schema
   
   
   
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [x] I have added tests corresponding to this change
   - [x] I have updated the documentation to reflect this change
   - [x] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-ingress-controller] tao12345666333 commented on a diff in pull request #1590: chore: update issue templates

[GitBox]

tao12345666333 commented on code in PR #1590:
URL: 
https://github.com/apache/apisix-ingress-controller/pull/1590#discussion_r1082165587


##
.github/ISSUE_TEMPLATE/improve_docs.yml:
##
@@ -0,0 +1,33 @@
+name: "Documentation Issue"
+description: Issues related to documentation.
+title: "docs: "
+labels: [doc]
+body:
+  - type: markdown
+attributes:
+  value: |
+_The more information you share, the faster we can help you._
+
+Prior to opening the issue, please make sure that you:
+
+- Use English to communicate.
+- Search the [open 
issues](https://github.com/apache/apisix-ingress-controller/issues) to avoid 
duplicating the issue.
+
+  - type: textarea
+id: current-state
+attributes:
+  label: Current State
+  description: Describe the current state of the documentation.
+  placeholder: |
+The documentation for the API in this page (url) is missing ...
+validations:
+  required: true
+  - type: textarea
+id: desired-state
+attributes:
+  label: Desired State
+  description: Describe the desired state the documentation should be in.
+  placeholder: |
+There should be line mentioning how the API behaves when ...

Review Comment:
   Ditto 



##
.github/ISSUE_TEMPLATE/improve_docs.yml:
##
@@ -0,0 +1,33 @@
+name: "Documentation Issue"
+description: Issues related to documentation.
+title: "docs: "
+labels: [doc]
+body:
+  - type: markdown
+attributes:
+  value: |
+_The more information you share, the faster we can help you._
+
+Prior to opening the issue, please make sure that you:
+
+- Use English to communicate.
+- Search the [open 
issues](https://github.com/apache/apisix-ingress-controller/issues) to avoid 
duplicating the issue.
+
+  - type: textarea
+id: current-state
+attributes:
+  label: Current State
+  description: Describe the current state of the documentation.
+  placeholder: |
+The documentation for the API in this page (url) is missing ...

Review Comment:
   For the function?



-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mgonzaga1990 commented on issue #8709: help request: Setting up routing path

[GitBox]

mgonzaga1990 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1397988920

   Hi @mscb402 ,
   
   **192.168.1.78:8090** is the address of the upstream and i have fixed it.
   now applying the below configuration
   
   ``` json
   {
 "uri": "/food/*",
 "name": "food-service-route",
 "methods": [
   "GET",
   "POST",
   "PUT",
   "DELETE",
   "PATCH",
   "HEAD",
   "OPTIONS",
   "CONNECT",
   "TRACE"
 ],
 "plugins": {
   "proxy-rewrite": {
 "regex_uri": [
   "^/food/(.*)",
   "/$1"
 ]
   }
 },
 "upstream_id": "443949312083231431",
 "status": 1
   }
   ```
   
   
![image](https://user-images.githubusercontent.com/21145779/213635779-ba5e1709-22a1-4f8e-906f-a79afc443e5d.png)
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #1608: bug: Block request method with Apisix Ingress Controller annotation

[GitBox]

tao12345666333 commented on issue #1608:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/1608#issuecomment-1397988082

   You mean the request should not be sent upstream, right?


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] Fabriceli commented on pull request #8651: fix: fix fetch all service info from consul

[GitBox]

Fabriceli commented on PR #8651:
URL: https://github.com/apache/apisix/pull/8651#issuecomment-1397953655

   @spacewander Please take a look at this PR, thanks


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[apisix-website] branch master updated: docs: add apisix with consul blog (#1478)

[sylviasu]

This is an automated email from the ASF dual-hosted git repository.

sylviasu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git


The following commit(s) were added to refs/heads/master by this push:
 new 428b481022e docs: add apisix with consul blog (#1478)
428b481022e is described below

commit 428b481022ea6fbec02534c7319aafdb675bbd60
Author: fabriceli 
AuthorDate: Fri Jan 20 13:50:16 2023 +0800

docs: add apisix with consul blog (#1478)

* feat: add apisix with consul

* feat: add apisix with consul

* feat: add apisix with consul

* feat: add apisix with consul

* feat: add apisix with consul

* feat: add apisix with consul

* fix cr

Co-authored-by: Fabriceli 
---
 blog/en/blog/2023/01/18/consul-with-apisix.md | 278 ++
 blog/zh/blog/2023/01/18/consul-with-apisix.md | 271 +
 2 files changed, 549 insertions(+)

diff --git a/blog/en/blog/2023/01/18/consul-with-apisix.md 
b/blog/en/blog/2023/01/18/consul-with-apisix.md
new file mode 100644
index 000..9a275b683fe
--- /dev/null
+++ b/blog/en/blog/2023/01/18/consul-with-apisix.md
@@ -0,0 +1,278 @@
+---
+title: "How to Integrate API Gateway and Consul? Not Consul K/V"
+authors:
+  - name: "Yihao LI"
+title: "Author"
+url: "https://github.com/Fabriceli";
+image_url: "https://github.com/Fabriceli.png";
+keywords:
+- API Gateway
+- Consul
+- Service Discovery
+- Service Register
+description: Apache APISIX supports the Consul service discovery registry. 
This article will walk you through the process of implementing service 
discovery and service registry in APISIX.
+tags: [Ecosystem]
+image: 
https://static.apiseven.com/2022/blog/0818/ecosystem/HashiCorp%20Consul.png
+---
+
+> Apache APISIX supports the Consul service discovery registry. This article 
will walk you through the process of implementing service discovery and service 
registry in Apache APISIX.
+
+
+
+## Background
+
+### About Apache APISIX
+
+Apache APISIX is an open source, dynamic, scalable, and high-performance cloud 
native API gateway for all your APIs and microservices.
+
+APISIX facilitates interface traffic handling for websites, mobile and IoT 
applications by providing services such as load balancing, dynamic upstream, 
canary release, fine-grained routing, rate limiting, and many more.
+
+### About Consul
+
+Consul is a distributed, highly available, and data center aware solution to 
connect and configure applications across dynamic, distributed infrastructure. 
Consul provides several key features: Multi-Datacenter, Service Mesh, Service 
Discovery, Health Checking, Key/Value Storage
+
+## Preparation Phase
+
+The test environments in this article are built in Docker using docker-compose.
+
+1. Download Apache APISIX
+
+  ```sh
+  git clone https://github.com/apache/apisix-docker.git
+  ```
+
+2. Create and run Consul
+
+  ```sh
+  docker run --rm --name consul_1 -d -p 8500:8500 consul:1.8 consul agent 
-server -bootstrap-expect=1 -node=agent-one -client 0.0.0.0 -log-level info 
-data-dir=/consul/data -enable-script-checks
+   ```
+
+3. Update Apache APISIX config file `apisix_conf/config.yaml`
+
+  ```yaml
+  # config.yml
+  # ... other config
+  discovery:
+consul:
+  servers:
+- "http://127.0.0.1:8500";
+  ```
+
+4. Start Apache APISIX
+
+  ```sh
+  # cd example folder，and start APISIX
+  docker-compose -f docker-compose.yml -p apisix-docker  up -d
+  ```
+
+5. Example contains two web services that you can use directly to test.
+
+  ```sh
+  sudo docker inspect -f='{{.Name}} - {{range 
.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $(sudo docker ps -aq) | grep 
web
+  # Outputs
+  /apisix-docker-web1-1 - 172.21.0.5
+  /apisix-docker-web2-1 - 172.21.0.6
+  ```
+
+6. Register the test service to Consul via Consul HTTP API.
+
+  ```shell
+  # Register with the corresponding IP and port
+  curl --location --request PUT 
'http://127.0.0.1:8500/v1/agent/service/register' \
+--header 'Content-Type: application/json' \
+--data '{
+"ID": "service_a1",
+"Name": "service_a",
+   "Tags": ["primary", "v1"],
+   "Address": "172.21.0.5",
+   "Port": 9081,
+   "Weights": {
+   "Passing": 10,
+   "Warning": 1
+   }
+}'
+
+  curl --location --request PUT 
'http://127.0.0.1:8500/v1/agent/service/register' \
+--header 'Content-Type: application/json' \
+--data '{
+  "ID": "service_a2",
+  "Name": "service_a",
+  "Tags": ["primary", "v1"],
+  "Address": "172.21.0.6",
+  "Port": 9082,
+  "Weights": {
+"Passing": 10,
+"Warning": 1
+  }
+   }'
+  ```
+
+7. Check whether the test service is registered successfully.
+
+  ```shell
+  curl --location --request GET 
'http://127.0.0.1:8500/v1/catalog/service/service_a'
+  ```
+
+   The URL `/v1/catalog/service/:service_name` end with the 

[GitHub] [apisix-website] SylviaBABY merged pull request #1478: docs: add apisix with consul blog

[GitBox]

SylviaBABY merged PR #1478:
URL: https://github.com/apache/apisix-website/pull/1478


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] Fabriceli commented on pull request #1478: docs: add apisix with consul blog

[GitBox]

Fabriceli commented on PR #1478:
URL: https://github.com/apache/apisix-website/pull/1478#issuecomment-1397944158

   @SylviaBABY @yzeng25 I have no permission to merge this PR, Could you merge 
it? 


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] navendu-pottekkat opened a new issue, #8715: docs: consolidate deployment modes guides

[GitBox]

navendu-pottekkat opened a new issue, #8715:
URL: https://github.com/apache/apisix/issues/8715

   ### Current State
   
   The [deployment modes documentation 
page](https://apisix.apache.org/docs/apisix/deployment-modes/) contains 
documentation about all the deployment modes. There is also another page for 
[stand-alone mode](https://apisix.apache.org/docs/apisix/stand-alone/) with 
just its documentation.
   
   ### Desired State
   
   Instead, these two pages should be merged to a single page and moved out of 
the "Others" section.


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[apisix-website] branch master updated: fix: front matter (#1482)

[young]

This is an automated email from the ASF dual-hosted git repository.

young pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git


The following commit(s) were added to refs/heads/master by this push:
 new 65cdc8bab57 fix: front matter (#1482)
65cdc8bab57 is described below

commit 65cdc8bab57d31f4144a428f0e9d597b94a3b383
Author: Young 
AuthorDate: Fri Jan 20 12:07:48 2023 +0800

fix: front matter (#1482)

Fixes https://github.com/apache/apisix-website/issues/1481
---
 ...from_everywhere_with_keycloak_authentication.md | 22 ++
 1 file changed, 10 insertions(+), 12 deletions(-)

diff --git 
a/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
 
b/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
index 468e91252f7..e464b8adcc4 100644
--- 
a/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
+++ 
b/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
@@ -2,7 +2,7 @@
 title: "Accessing APISIX-Dashboard from Everywhere with Keycloak 
Authentication"
 authors:
   - name: "Busico Mirto Silvio"
-title: ""
+title: "Author"
 url: "https://github.com/MirtoBusico";
 image_url: 
"https://avatars.githubusercontent.com/u/11090934?s=400&u=644e4f87c2fad56760f6eb4f46cbcb4db059880a&v=4";
 keywords:
@@ -13,9 +13,7 @@ keywords:
   - Keycloak
 description: This guest blog shares how to expose the APISIX Dashboard using 
APISIX to authenticate access with the OpenID-Connect plugin and Keycloak 
server to manage identities.
 tags:
-  - APISIX Basics
-  - API Gateway Concepts
-  - Authorization & Authentication
+  - Ecosystem
 cover: https://static.apiseven.com/uploads/2023/01/19/FKDU7U6j_blog01a.png
 ---
 
@@ -37,14 +35,14 @@ Here I'll present instructions, examples, code and 
screenshots taken from my hom
 
 The framework used in this article consists of some KVM virtual machines (from 
now VM):
 
-| VM Name | Role | Services | Description |
-|-|--|--|-|
-|   hdev  |  Development|kubectl, istioctl, helm  | 
workstation from where manage the cluster   |
-|   hserv |  external services| DNS server, Nginx, Keycloak  | 
services used by the cluster VM and external users|
-|   hkm   | Kubernetes master | master node | control plane 
manager for K8S|
-|   hkw1  | K8S worker 1| first worker node | node for 
hosting pods|
-|   hkw2  | K8S worker 2| second worker node | node for 
hosting pods|
-|   hkw3  | K8S worker 3| third worker node | node for 
hosting pods|
+| VM Name | Role  | Services| Description  
  |
+| --- | - | --- | 
-- |
+| hdev| Development   | kubectl, istioctl, helm | workstation from 
where manage the cluster  |
+| hserv   | external services | DNS server, Nginx, Keycloak | services used by 
the cluster VM and external users |
+| hkm | Kubernetes master | master node | control plane 
manager for K8S  |
+| hkw1| K8S worker 1  | first worker node   | node for hosting 
pods  |
+| hkw2| K8S worker 2  | second worker node  | node for hosting 
pods  |
+| hkw3| K8S worker 3  | third worker node   | node for hosting 
pods  |
 
 The **hserv** VM have two lan cards: one on an external lan to expose services 
and one an internal lan to communicate with the Kubernetes (from now K8S) 
cluster.
 All the other VM are only connected to the internal lan.

[GitHub] [apisix-website] SkyeYoung closed issue #1481: [Site]: Blog "Accessing APISIX-Dashboard from Everywhere with Keycloak Authentication" not accessible

[GitBox]

SkyeYoung closed issue #1481: [Site]: Blog "Accessing APISIX-Dashboard from 
Everywhere with Keycloak Authentication" not accessible
URL: https://github.com/apache/apisix-website/issues/1481


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] SkyeYoung merged pull request #1482: fix: front matter

[GitBox]

SkyeYoung merged PR #1482:
URL: https://github.com/apache/apisix-website/pull/1482


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] netlify[bot] commented on pull request #1482: fix: front matter

[GitBox]

netlify[bot] commented on PR #1482:
URL: https://github.com/apache/apisix-website/pull/1482#issuecomment-1397880770

   ### 👷 Deploy Preview for *apache-apisix* 
processing.
   
   
   |  Name | Link |
   |-||
   |🔨 Latest commit | 
e5502f779ec7b82d8df8a951c1df2ce42338268e |
   |🔍 Latest deploy log | 
https://app.netlify.com/sites/apache-apisix/deploys/63ca09d27c16330008635a25 |


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] SkyeYoung opened a new pull request, #1482: fix: front matter

[GitBox]

SkyeYoung opened a new pull request, #1482:
URL: https://github.com/apache/apisix-website/pull/1482

   Fixes: #1481 
   Changes:
   
   * add missing author
   
   
   Screenshots of the change:
   
   
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] Fabriceli commented on a diff in pull request #1478: docs: add apisix with consul blog

[GitBox]

Fabriceli commented on code in PR #1478:
URL: https://github.com/apache/apisix-website/pull/1478#discussion_r1082069199


##
blog/en/blog/2023/01/18/consul-with-apisix.md:
##
@@ -0,0 +1,274 @@
+---
+title: "How to Integrate API Gateway and Consul? Not Consul K/V"
+authors:
+  - name: "Yihao LI"
+title: "Author"
+url: "https://github.com/Fabriceli";
+image_url: "https://github.com/Fabriceli.png";
+keywords:
+- API Gateway
+- Consul
+- Service Discovery
+- Service Register
+description: Apache APISIX supports the Consul service discovery registry. 
This article will walk you through the process of implementing service 
discovery and service registry in APISIX.
+tags: [Ecosystem]
+image: 
https://static.apiseven.com/2022/blog/0818/ecosystem/HashiCorp%20Consul.png
+---
+

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.

To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] SylviaBABY merged pull request #8714: docs: fix deployment doc links

[GitBox]

SylviaBABY merged PR #8714:
URL: https://github.com/apache/apisix/pull/8714


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] SkyeYoung closed issue #8698: [docs]: deployment-role.md is not exist

[GitBox]

SkyeYoung closed issue #8698: [docs]: deployment-role.md is not exist
URL: https://github.com/apache/apisix/issues/8698


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] SkyeYoung commented on issue #8698: [docs]: deployment-role.md is not exist

[GitBox]

SkyeYoung commented on issue #8698:
URL: https://github.com/apache/apisix/issues/8698#issuecomment-1397862577

   fixed in #8714 


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[apisix] branch master updated: docs: fix deployment links (#8714)

[sylviasu]

This is an automated email from the ASF dual-hosted git repository.

sylviasu 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 9e19dcc01 docs: fix deployment links (#8714)
9e19dcc01 is described below

commit 9e19dcc013463c9c00ad9988059b0c72f1f13fca
Author: Sylvia <39793568+sylviab...@users.noreply.github.com>
AuthorDate: Fri Jan 20 10:50:42 2023 +0800

docs: fix deployment links (#8714)
---
 docs/en/latest/certificate.md | 2 +-
 docs/zh/latest/certificate.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/en/latest/certificate.md b/docs/en/latest/certificate.md
index 4bcfa5ae2..f5f9c8cce 100644
--- a/docs/en/latest/certificate.md
+++ b/docs/en/latest/certificate.md
@@ -174,7 +174,7 @@ pair. So the length of `certs` and `keys` must be same.
 
 ### set up multiple CA certificates
 
-APISIX currently uses CA certificates in several places, such as [Protect 
Admin API](./mtls.md#protect-admin-api), [etcd with 
mTLS](./mtls.md#etcd-with-mtls), and [Deployment 
Modes](./architecture-design/deployment-role.md).
+APISIX currently uses CA certificates in several places, such as [Protect 
Admin API](./mtls.md#protect-admin-api), [etcd with 
mTLS](./mtls.md#etcd-with-mtls), and [Deployment Modes](./deployment-modes.md).
 
 In these places, `ssl_trusted_certificate` or `trusted_ca_cert` will be used 
to set up the CA certificate, but these configurations will eventually be 
translated into 
[lua_ssl_trusted_certificate](https://github.com/openresty/lua-nginx-module#lua_ssl_trusted_certificate)
 directive in OpenResty.
 
diff --git a/docs/zh/latest/certificate.md b/docs/zh/latest/certificate.md
index 310f53890..d1322bb65 100644
--- a/docs/zh/latest/certificate.md
+++ b/docs/zh/latest/certificate.md
@@ -171,7 +171,7 @@ curl --resolve 'www.test.com:9443:127.0.0.1' 
https://www.test.com:9443/hello  -v
 
 ### 设置多个 CA 证书
 
-APISIX 目前支持在多处设置 CA 证书，比如 [保护 Admin API](./mtls.md#保护-admin-api)，[保护 
ETCD](./mtls.md#保护-etcd)，以及 
[部署模式](../../en/latest/architecture-design/deployment-role.md) 等。
+APISIX 目前支持在多处设置 CA 证书，比如 [保护 Admin API](./mtls.md#保护-admin-api)，[保护 
ETCD](./mtls.md#保护-etcd)，以及 [部署模式](../../en/latest/deployment-modes.md) 等。
 
 在这些地方，使用 `ssl_trusted_certificate` 或 `trusted_ca_cert` 来配置 CA 证书，但是这些配置最终将转化为 
OpenResty 的 
[lua_ssl_trusted_certificate](https://github.com/openresty/lua-nginx-module#lua_ssl_trusted_certificate)
 指令。
 

[GitHub] [apisix] SylviaBABY opened a new pull request, #8714: docs: fix deployment links

[GitBox]

SylviaBABY opened a new pull request, #8714:
URL: https://github.com/apache/apisix/pull/8714

   ### Description
   
   
   
   
   Fixes # https://github.com/apache/apisix/issues/8698, update ZH/EN docs link
   
   ### Checklist
   
   - [ ] I have explained the need for this PR and the problem it solves
   - [ ] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change
   - [ ] I have updated the documentation to reflect this change
   - [ ] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] yzeng25 commented on a diff in pull request #1478: docs: add apisix with consul blog

[GitBox]

yzeng25 commented on code in PR #1478:
URL: https://github.com/apache/apisix-website/pull/1478#discussion_r1082065305


##
blog/en/blog/2023/01/18/consul-with-apisix.md:
##
@@ -0,0 +1,274 @@
+---
+title: "How to Integrate API Gateway and Consul? Not Consul K/V"
+authors:
+  - name: "Yihao LI"
+title: "Author"
+url: "https://github.com/Fabriceli";
+image_url: "https://github.com/Fabriceli.png";
+keywords:
+- API Gateway
+- Consul
+- Service Discovery
+- Service Register
+description: Apache APISIX supports the Consul service discovery registry. 
This article will walk you through the process of implementing service 
discovery and service registry in APISIX.
+tags: [Ecosystem]
+image: 
https://static.apiseven.com/2022/blog/0818/ecosystem/HashiCorp%20Consul.png
+---
+

Review Comment:
   1. Need a `` here to cut actual contents off from the blog 
summary page
   2. Need a sentence or two to add a summary for this blog.
   ```suggestion
   > This article teaches you how to integrate Consul with Apache APISIX 
   
   
   ```
   Now it looks like this, and it is just not right.
   
   
![image](https://user-images.githubusercontent.com/36651058/213606541-05dafa7c-9119-4419-99be-df1a293d1f63.png)
   
   



-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[apisix-website] branch master updated: docs: add weekly report 20230115 (#1479)

[yilinzeng]

This is an automated email from the ASF dual-hosted git repository.

yilinzeng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git


The following commit(s) were added to refs/heads/master by this push:
 new aa07a5e15bb docs: add weekly report 20230115 (#1479)
aa07a5e15bb is described below

commit aa07a5e15bb2fd6297130856d54a2487c73e6e9d
Author: 长龙 <362753...@qq.com>
AuthorDate: Fri Jan 20 10:32:43 2023 +0800

docs: add weekly report 20230115 (#1479)
---
 blog/zh/blog/2023/01/19/weekly-report-0115.md | 63 +++
 1 file changed, 63 insertions(+)

diff --git a/blog/zh/blog/2023/01/19/weekly-report-0115.md 
b/blog/zh/blog/2023/01/19/weekly-report-0115.md
new file mode 100644
index 000..de16498cbed
--- /dev/null
+++ b/blog/zh/blog/2023/01/19/weekly-report-0115.md
@@ -0,0 +1,63 @@
+---
+title: "社区双周报 (1.2 - 1.15)"
+keywords: 
+- Apache APISIX
+- API 网关
+- 社区周报
+- 贡献者
+description: “独行者速，众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 
社区的进展，方便大家参与到 Apache APISIX 社区中来。
+tags: [Community]
+image: 
https://static.apiseven.com/uploads/2023/01/19/l4EyvNRI_%E7%A4%BE%E5%8C%BA%E5%8F%8C%E5%91%A8%E6%8A%A5-%E5%A4%B4%E5%9B%BE-01%E5%91%A8.png
+---
+
+> 从 2023.1.2 - 2023.1.15，有 19 位开发者为 Apache APISIX 提交了 33 个 commit。感谢这些小伙伴为 
Apache APISIX 添砖加瓦，是你们的无私付出，让 Apache APISIX 项目变得更好！
+
+
+
+## 导语
+
+Apache APISIX 从开源第一天就以社区方式成长，迅速成为全世界最活跃的开源 API 网关项目。这些成就，离不开社区小伙伴们的共同奋斗。
+
+“独行者速，众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的进展，方便大家参与到 
Apache APISIX 社区中来。
+
+**值得一提的是，新晋贡献者来自多个国家（波兰、巴基斯坦、挪威、越南），APISIX 正在被世界各地有趣的开发者们关注并参与贡献。**
+
+## 贡献者统计
+
+![贡献者名单](https://static.apiseven.com/uploads/2023/01/19/ttc04wzr_%E7%A4%BE%E5%8C%BA%E5%8F%8C%E5%91%A8%E6%8A%A5-%E8%B4%A1%E7%8C%AE%E8%80%85%E6%B5%B7%E6%8A%A5-01%E5%91%A8.png)
+
+![新晋贡献者](https://static.apiseven.com/uploads/2023/01/19/m0C82lr9_%E7%A4%BE%E5%8C%BA%E5%8F%8C%E5%91%A8%E6%8A%A5-%E6%96%B0%E6%99%8B%E6%B5%B7%E6%8A%A5-01%E5%91%A8.png)
+
+## 近期功能特性亮点
+
+- [`limit-count` 插件添加 Redis 集群 TLS/SSL 
连接模式支持。](https://github.com/apache/apisix/pull/8558)（贡献者：[ronething](https://github.com/ronething)）
+
+- [`limit-count` 插件添加 `X-RateLimit-Reset` 
支持。](https://github.com/apache/apisix/pull/8578)（贡献者：[mscb402](https://github.com/mscb402)）
+
+- [Logger 
类插件支持定制化日志格式。](https://github.com/apache/apisix/pull/8583)（贡献者：[spacewander](https://github.com/spacewander)）
+
+- [Stream 代理模式添加 Eureka 
服务发现支持。](https://github.com/apache/apisix/pull/8583)（贡献者：[ronething](https://github.com/ronething)）
+
+- [Stream 代理模式添加 DNS 
服务发现支持。](https://github.com/apache/apisix/pull/8593)（贡献者：[ronething](https://github.com/ronething)）
+
+- [Stream 代理模式添加 Nacos 
服务发现支持。](https://github.com/apache/apisix/pull/8584)（贡献者：[ronething](https://github.com/ronething)）
+
+Apache APISIX 的项目官网和 Github 上的 Issue 上已经积累了比较丰富的文档教程和使用经验，如果您遇到问题可以翻阅文档，用关键词在 
Issue 中搜索，也可以参与 Issue 上的讨论，提出自己的想法和实践经验。
+
+## 近期博文推荐
+
+- [马蜂窝如何利用 APISIX 
网关实现微服务架构升级](https://apisix.apache.org/zh/blog/2023/01/15/mafengwo-with-apisix/)
+
+本文从马蜂窝的微服务架构平台蜂效迭代过程和应用 APISIX 后的产品实践角度，为大家呈现了基于 APISIX 的网关应用实例。
+
+- [Apache APISIX Ingress 1.6 
正式发布](https://apisix.apache.org/zh/blog/2023/01/10/release-apisix-ingress-1.6/)
+
+Apache APISIX Ingress 1.6 版本正式发布！此版本带来了 Gateway API 
的支持，同时新增服务发现组件集成与代理外部服务，优化对 APISIX Ingress Controller 的使用体验。
+
+- [2022 Apache APISIX 
年度记忆](https://apisix.apache.org/zh/blog/2023/01/02/2022-summary/)
+
+本文将带您回顾 Apache APISIX 社区在 2022 年在各领域取得的成绩。
+
+- [Apache APISIX 3.1.0 
正式发布](https://apisix.apache.org/zh/blog/2022/12/30/release-apache-apisix-3.1.0/)
+
+Apache APISIX 3.1.0 版本正式发布！此版本带来很多关于安全层面的功能支持，同时新增内置调试插件，旨在优化对 APISIX 
的使用体验。

[GitHub] [apisix-website] yzeng25 merged pull request #1479: docs: add weekly report 20230115

[GitBox]

yzeng25 merged PR #1479:
URL: https://github.com/apache/apisix-website/pull/1479


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] yzeng25 opened a new issue, #1481: [Site]: Blog "Accessing APISIX-Dashboard from Everywhere with Keycloak Authentication" not accessible

[GitBox]

yzeng25 opened a new issue, #1481:
URL: https://github.com/apache/apisix-website/issues/1481

   ### Current State
   
   **Description of the current state/issue**:
   
   Blog "Accessing APISIX-Dashboard from Everywhere with Keycloak 
Authentication" was added into the website via 
https://github.com/apache/apisix-website/pull/1468. But it is not accessible 
after merging.
   
   **Link to the page**:
   
   none
   
   **Steps to reproduce**
   
   **Actual behavior**
   
   Take the most recent English post as an example, the href should be: 
https://apisix.apache.org/blog/2022/12/30/release-apache-apisix-3.1.0/, in 
which:
   
   - `https://apisix.apache.org/blog/` is the prefix, fixed value fore each and 
every blog;
   - `2022/12/30/release-apache-apisix-3.1.0/` is the suffix, is generated from 
the file name.
   
   After merging https://github.com/apache/apisix-website/pull/1468, the blog 
is not showing up on the Blog summary page.
   
   Accessing the actual href 
`https://apisix.apache.org/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md`
 gives a `300` status with a 'Mutiple Choice' notification, see image below.
   
   
![image](https://user-images.githubusercontent.com/36651058/213604162-2ba0f856-f20e-4886-bc93-b310a3952f05.png)
   
   Then, all three options from the multiple choices return 404. As a result, 
this blog is not accessible.
   
   **Expected behavior**
   1. This blog shows up in the blog summary page.
   2. This blog is accessible, i.e. click the link and jump to blog content 
page.
   
   
   **Screenshots (if relevant)**:
   
   
![image](https://user-images.githubusercontent.com/36651058/213604664-527ac7ff-4ace-48b2-8ac0-35beba873459.png)
   
   
   
   ### Desired State
   
   **Description of the change you are proposing**:
   
   1. This blog shows up in the blog summary page.
   2. This blog is accessible, i.e. click the link and jump to blog content 
page.
   
   I think fixing the header part should fix this issue.
   
   ### Would you like to fix this issue?
   
   No. Please assign another contributor


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-website] yzeng25 commented on pull request #1468: Add blog post "Accessing Apisix-dashboard from everywhere with Keycloak authentication"

[GitBox]

yzeng25 commented on PR #1468:
URL: https://github.com/apache/apisix-website/pull/1468#issuecomment-1397839408

   Hi, this blog isn't showing up properly in the website. Probably need to fix 
the header part to fix this issue. The blog content part was great. You guys 
should at least check out the preview link before giving approvals and merging 
next time. @juzhiyuan @guoqqqi 


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1397820999

   Please make sure your upstream is working.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1397819842

   This just your upstream time out. Please chekout


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1397819303

   Are you config the upstream address wrong? Dose 192.168.1.78:8090 is an 
APISIX instance?


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] MarkCupitt commented on issue #8663: bug: failed to find any SSL certificate by SNI:

[GitBox]

MarkCupitt commented on issue #8663:
URL: https://github.com/apache/apisix/issues/8663#issuecomment-1397802057

   Certs loaded by the dashboard V2 will NOT be seen in the routing, until the 
dashboard is made compatible, you MUST use the API's to load and manage certs
   
   Additionally, if you use a Wildcard Cert ["*.example.com"] the route MUST 
use `hosts: ["*.example.com"]`. if you need granular route matching, you will 
need to add a filter, or match on vars and/or priority
   
   if you use `host: "my.example.com"` it will not match, is it uses the 
literal SNI value `*.example.com`
   
   @tokers Might save a lot of grief for people if this could be added to the 
documentation in the following locations:
   
   https://apisix.apache.org/docs/apisix/admin-api/#request-body-parameters
   https://apisix.apache.org/docs/apisix/admin-api/#ssl-api
   
   Documenting in case anyone else has this issue


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[apisix-dashboard] branch master updated: fix: adapt APISIX plugin disabled (#2717)

[baoyuan]

This is an automated email from the ASF dual-hosted git repository.

baoyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-dashboard.git


The following commit(s) were added to refs/heads/master by this push:
 new 7b8d9c5b3 fix: adapt APISIX plugin disabled (#2717)
7b8d9c5b3 is described below

commit 7b8d9c5b30a8eae2ca038b99cf2a3c36cdca2ddc
Author: Baoyuan 
AuthorDate: Fri Jan 20 09:02:44 2023 +0800

fix: adapt APISIX plugin disabled (#2717)
---
 web/.eslintrc.js   |  1 +
 web/src/components/Plugin/PluginDetail.tsx |  6 --
 web/src/components/Plugin/PluginPage.tsx   | 10 +-
 3 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/web/.eslintrc.js b/web/.eslintrc.js
index 36fbf31f6..2f2bd7682 100644
--- a/web/.eslintrc.js
+++ b/web/.eslintrc.js
@@ -33,6 +33,7 @@ module.exports = {
 'import/order': 'off',
 'simple-import-sort/imports': 'error',
 'simple-import-sort/exports': 'error',
+'no-underscore-dangle': 'off',
   },
   settings: {
 'import/resolver': {
diff --git a/web/src/components/Plugin/PluginDetail.tsx 
b/web/src/components/Plugin/PluginDetail.tsx
index 8fc98acd7..0e0fc8f96 100644
--- a/web/src/components/Plugin/PluginDetail.tsx
+++ b/web/src/components/Plugin/PluginDetail.tsx
@@ -181,7 +181,7 @@ const PluginDetail: React.FC = ({
 
   useEffect(() => {
 form.setFieldsValue({
-  disable: isEnabled ? true : initialData[name] && 
!initialData[name].disable,
+  disable: isEnabled ? true : initialData[name] && 
!initialData[name]._meta.disable,
   scope: 'global',
 });
 if (PLUGIN_UI_LIST.includes(name)) {
@@ -415,7 +415,9 @@ const PluginDetail: React.FC = ({
   name="disable"
 >
   
 
diff --git a/web/src/components/Plugin/PluginPage.tsx 
b/web/src/components/Plugin/PluginPage.tsx
index 62460cf1e..5c843f3c3 100644
--- a/web/src/components/Plugin/PluginPage.tsx
+++ b/web/src/components/Plugin/PluginPage.tsx
@@ -101,7 +101,7 @@ const PluginPage: React.FC = ({
 
   useEffect(() => {
 const openPluginList = pluginList.filter(
-  (item) => initialData[item.name] && !initialData[item.name].disable,
+  (item) => initialData[item.name] && 
!initialData[item.name]._meta.disable,
 );
 setPlugins(initialData);
 setEnablePluginsList(openPluginList);
@@ -244,16 +244,16 @@ const PluginPage: React.FC = ({
   actions={[
  {
 setName(item.name);
   }}
 >
-  {initialData[item.name] && 
!initialData[item.name].disable
+  {initialData[item.name] && 
!initialData[item.name]._meta.disable
 ? formatMessage({ id: 'component.plugin.disable' })
 : formatMessage({ id: 'component.plugin.enable' })}
 ,
@@ -315,7 +315,7 @@ const PluginPage: React.FC = ({
   onChange={({ monacoData, formData, shouldDelete }) => {
 let newPlugins = {
   ...initialData,
-  [name]: { ...monacoData, disable: !formData.disable },
+  [name]: { ...monacoData, _meta: { disable: !formData.disable } },
 };
 let handleType = 'edit';
 if (shouldDelete === true) {

[GitHub] [apisix-dashboard] Baoyuantop merged pull request #2717: fix: adapt APISIX plugin disabled

[GitBox]

Baoyuantop merged PR #2717:
URL: https://github.com/apache/apisix-dashboard/pull/2717


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] MarkCupitt closed issue #8665: bug: uploading a cert via api - it is accepted with no error, shows in dashboard with correct SNI, but invalid expiry date. Cert can NOT be deleted

[GitBox]

MarkCupitt closed issue #8665: bug: uploading a cert via api - it is accepted 
with no error, shows in dashboard with correct SNI, but invalid expiry date. 
Cert can NOT be deleted
URL: https://github.com/apache/apisix/issues/8665


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] MarkCupitt commented on issue #8665: bug: uploading a cert via api - it is accepted with no error, shows in dashboard with correct SNI, but invalid expiry date. Cert can NOT be delet

[GitBox]

MarkCupitt commented on issue #8665:
URL: https://github.com/apache/apisix/issues/8665#issuecomment-1397796190

   So for those struggling with this, Dashboard V2, on ssl certs at least, is 
NOT compatible at all with apisix V3.x, you **MUST** use the apis.
   
   Documenting for anyone else who may come across this issue
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] MarkCupitt commented on issue #8665: bug: uploading a cert via api - it is accepted with no error, shows in dashboard with correct SNI, but invalid expiry date. Cert can NOT be delet

[GitBox]

MarkCupitt commented on issue #8665:
URL: https://github.com/apache/apisix/issues/8665#issuecomment-1397778959

   Additional effort still produces same result, 
   
   Bash Script used:
   
   ```
 local sslcrt=$(cat "./certs/$sslurl.crt")
 local sslkey=$(cat "./certs/$sslurl.key")
 
 local json=$(cat /dev/null
   ```
   Note on image:
   
   - Cert loaded via APi
   - Expiration time not decoded
   - SNI Decoded
   - Unable to delete. Noted its using /ssl and not ssls
   
   
![image](https://user-images.githubusercontent.com/5503184/213591433-2066d6c4-0e73-41f7-abae-5c2bb5196949.png)
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-ingress-controller] hndoss opened a new issue, #1608: bug: Block request method with Apisix Ingress Controller annotation

[GitBox]

hndoss opened a new issue, #1608:
URL: https://github.com/apache/apisix-ingress-controller/issues/1608

   ### Issue description
   
   After implementing the new annotations, the affected Apisix Route has a 
plugin configuration as follows:
   ```
   "response-rewrite": {
 "body_base64": false,
 "status_code": 405,
 "vars": [
   [
 "request_method",
 "!",
 "in",
 [
   "GET",
   "POST",
   "PUT",
   "PATCH",
   "HEAD"
 ]
   ]
 ]
   }
   ```
   
   The plugin is `response-rewrite`. This plugin just overwrites the response 
from the Upstream. Meaning that, any DELETE will succeed, and Apisix will just 
overwrite the HTTP to a 405.
   
   Can 
[request-validation](https://apisix.apache.org/docs/apisix/plugins/request-validation/)
 plugin be used instead?
   
   ---
   Related 
[issue](https://github.com/apache/apisix-ingress-controller/issues/1463)
   
   ### Environment
   
   - your apisix-ingress-controller version (output of 
apisix-ingress-controller version --long):
   ```
   /ingress-apisix # /ingress-apisix/apisix-ingress-controller version --long
   Version: 1.6.0
   Git SHA: no-git-module
   Go Version: go1.19.4
   Building OS/Arch: linux/amd64
   Running OS/Arch: linux/amd64
   ```
   
   - your Kubernetes cluster version (output of kubectl version):
   ```
   Client Version: v1.25.4
   Kustomize Version: v4.5.7
   Server Version: v1.21.14-gke.3000
   ```
   
   - if you run apisix-ingress-controller in Bare-metal environment, also show 
your OS version (uname -a):
   
   
   ### Minimal test code / Steps to reproduce
   
   1. Create an ingress using Allow [http methods 
annotations](https://apisix.apache.org/docs/ingress-controller/concepts/annotations/#allow-http-methods)
   2. Attempt to use an HTTP method that is it white listed
   
   ### Actual result
   
   curl -I  -X DELETE https://my-domain.io/my-service/1
   HTTP/2 405 
   date: Thu, 19 Jan 2023 19:11:55 GMT
   content-type: application/vnd.schemaregistry.v1+json
   content-length: 4
   
   ### Error log
   
   curl -I  -X DELETE https://my-domain.io/my-service/1
   {"error_code":40404,"message":"Subject 1 was soft deleted.Set permanent=true 
to delete permanently"}
   
   ### Expected result
   
   The  https://my-domain.io/my-service/1 should be present since it is not 
possible to DELETE


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-docker] incubator4 opened a new pull request, #412: fix: apisix config etcd indent error

[GitBox]

incubator4 opened a new pull request, #412:
URL: https://github.com/apache/apisix-docker/pull/412

   Due to apisix `config.yaml` indent error, etcd configuration didn't 
passthrought to apisix,  it would cause problem that apisix use default config 
to connect etcd by `127.0.0.1:2379`


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-dashboard] LiteSun commented on a diff in pull request #2704: fix plugins display in list of routes

[GitBox]

LiteSun commented on code in PR #2704:
URL: https://github.com/apache/apisix-dashboard/pull/2704#discussion_r1081381117


##
web/src/pages/Route/List.tsx:
##
@@ -550,6 +551,13 @@ const Page: React.FC = () => {
 {
   title: formatMessage({ id: 'menu.plugin' }),
   dataIndex: 'plugins',
+  width: 240,
+  render: (_, record) => {
+const plugins = record.plugins || {};
+return Object.keys(plugins).length > 0
+  ? Object.keys(plugins).map((key) =>  {key})

Review Comment:
   ```suggestion
 ? Object.keys(plugins).map((key) => {key})
   ```



-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mgonzaga1990 commented on issue #8709: help request: Setting up routing path

[GitBox]

mgonzaga1990 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1397020304

   Now I'm getting **504 Gateway timeout**
   
![image](https://user-images.githubusercontent.com/21145779/213460809-18921094-cf4e-4066-9d4a-d88cea34b789.png)
   
   and based on the log
   ```
   2023/01/19 13:53:24 [error] 51#51: *310593 upstream timed out (110: 
Operation timed out) while connecting to upstream, client: 172.18.0.1, server: 
_, request: "GET /food/v1/dishes HTTP/1.1", upstream: 
"http://192.168.1.78:8090/food/v1/dishes";, host: "localhost:9080"
   ```
   it is forwarding "http://192.168.1.78:8090/food/v1/dishes"; and 
/food/v1/dishes dosent exists in port 8090
   
   
![image](https://user-images.githubusercontent.com/21145779/213460756-36d99f8b-004f-410d-a35c-c17547fa7448.png)
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-ingress-controller] navendu-pottekkat opened a new pull request, #1607: docs: add Gateway API example to the "Getting started" guide

[GitBox]

navendu-pottekkat opened a new pull request, #1607:
URL: https://github.com/apache/apisix-ingress-controller/pull/1607

   Signed-off-by: Navendu Pottekkat 
   
   Add an example of the Gateway API to the "Getting started" guide.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-docker] sbrouet opened a new issue, #411: Not same user (root VS apisix) used depending on Linux distribution

[GitBox]

sbrouet opened a new issue, #411:
URL: https://github.com/apache/apisix-docker/issues/411

   Hello Team,
   
   I noticed that for some Docker images, the `root`  user is used, such as 
`centos`.
   For others the `apisix` user is used, such as for `debian`.
   This could lead to different behavior since user rights are different, so 
something that would work in `centos` Docker image would fail in `debian` one.
   
   -> Suggestion: use applicative `apisix` in all Docker images and same user 
rights on directories
   
   Thank you,
   Sébastien


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-docker] sbrouet opened a new issue, #410: Possible fix in entrypoint.sh - hardcoded path

[GitBox]

sbrouet opened a new issue, #410:
URL: https://github.com/apache/apisix-docker/issues/410

   Hello Team,
   
   In entrypoint.sh for debian, at line 43 the path to configuration directory 
is hardcoded to `/usr/local/apisix`
   
   See 
https://github.com/apache/apisix-docker/blob/master/debian/docker-entrypoint.sh#L43
   ```
   exec /usr/local/openresty/bin/openresty -p /usr/local/apisix -g 'daemon off;'
   ```
   
   But configuration directory can be configured with variable PREFIX which is 
declared at beginning of script and used for some commands, for initializing 
configuration:
   ```
   PREFIX=${APISIX_PREFIX:=/usr/local/apisix}
   [...]
   cat > ${PREFIX}/conf/config.yaml << _EOC_
   [...]
   cat > ${PREFIX}/conf/apisix.yaml << _EOC_
   ```
   
   -> It seems to me that variable should be used also in exec command show 
above, which would look like:
   ```
   exec /usr/local/openresty/bin/openresty -p ${PREFIX} -g 'daemon off;'
   ```
   
   If change is needed, must be done in all `docker-entrypoint.sh` files in Git 
repository.
   
   Thank you,
   Sébastien
   


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-ingress-controller] tao12345666333 closed issue #1547: chore: improve make update-all

[GitBox]

tao12345666333 closed issue #1547: chore: improve make update-all 
URL: https://github.com/apache/apisix-ingress-controller/issues/1547


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-helm-chart] tao12345666333 commented on issue #454: doc: Fix standalone mode FAQ

[GitBox]

tao12345666333 commented on issue #454:
URL: 
https://github.com/apache/apisix-helm-chart/issues/454#issuecomment-1396939889

   Thanks! Would you like to open a PR for this?


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-docker] shivahnshankar commented on issue #409: Discuss: unable to pull arm64 etcd image correctly on M1 arm arch

[GitBox]

shivahnshankar commented on issue #409:
URL: https://github.com/apache/apisix-docker/issues/409#issuecomment-1396919772

   I even tried `pachyderm/etcd` and `docker/desktop-kubernetes-etcd`. The etcd 
service starts but the dashboard fails to connect to the service. 
   I am exploring whether this is the issue: 
[https://github.com/etcd-io/etcd/issues/10677#issuecomment-660935539](https://github.com/etcd-io/etcd/issues/10677#issuecomment-660935539)
 in etcd_data mount


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix-helm-chart] sbrouet opened a new issue, #454: doc: Fix standalone mode FAQ

[GitBox]

sbrouet opened a new issue, #454:
URL: https://github.com/apache/apisix-helm-chart/issues/454

   Hello Team,
   
   I spent some time trying to have standalone mode working on Kubernetes.
   I used information from the official Helm Chart FAQ here: 
https://github.com/apache/apisix-helm-chart/blob/master/docs/en/latest/FAQ.md#how-to-install-apache-apisix-running-in-standalone-mode
   
   I found out several issues, and also would like to propose some remarks and 
changes.
   I'll explain all of them here, please feel free to comment.
   If adequate we can create separate issues and close this one.
   
   ### Issue 1: sample Kubernetes files out of date
    Issue 1.1 : to be removed: sample with alpine based Docker image
   Alpine docker image have been removed from apisix-docker repository (see 
https://github.com/apache/apisix-docker and 
https://github.com/apache/apisix-docker/pull/395)
   -> Recommendation: remove sample with alpine docker image
   
    Issue 1.2 : sample with centos based Docker image not working, but OK 
with debian
   When using exact sample file, the Apisix gateway pod does start, but the 
routes configuration file (apisix.yaml) is not present while it is supposely 
mounted by the deployment in `/apisix-config/` directory
   ```
   # From inside pod:
   ~ # find / -name apisix.yaml
   ~ # ls -l /apisix-config/
   ls: /apisix-config/: No such file or directory
   ```
   
   The `apisix.yaml` file located in `/usr/local/apisix/conf/` contains default 
file with empty routes list, instead of being replaced by symbolic link from 
/apisix-config/apisix.yaml.
   
   When running exact same file and just changing the docker image to a debian 
one, it worked perfectly:
   ```
   image: "apache/apisix:3.1.0-debian"
   ```
   Thank you @AlinsRan for you advice.
   -> Recommendation: change centos example to debian
   
   
   ### Issue 2:  possible fix in entrypoint.sh
   In entrypoint.sh for debian, at line 43 the path to configuration directory 
is hardcoded to `/usr/local/apisix`
   See 
https://github.com/apache/apisix-docker/blob/master/debian/docker-entrypoint.sh#L43
   ```
   exec /usr/local/openresty/bin/openresty -p /usr/local/apisix -g 'daemon off;'
   ```
   But configuration directory can be configured with variable  PREFIX which is 
declared at begining of script and used for some commands, for initializing 
configuration
   ```
   PREFIX=${APISIX_PREFIX:=/usr/local/apisix}
   [...]
   cat > ${PREFIX}/conf/config.yaml << _EOC_
   [...]
   cat > ${PREFIX}/conf/apisix.yaml << _EOC_
   ```
   
   -> It seems to me that variable should be used also in exec command show 
above, which would look like:
   ```
   exec /usr/local/openresty/bin/openresty -p ${PREFIX} -g 'daemon off;'
   ```
   If change is needed, must be done in all `docker-entrypoint.sh` files in Git 
repository.
   
   
   ### Issue 3: add recommendation for Linux distribution to be used
   Samples in FAQ for standalone mode propose different distributions.
   Official Helm Chart uses debian based docker image
   -> Suggestion: clarify in FAQ what should be recommended distribution. Seems 
logical to me it should be same one as Helm Charts. Also if any specifics are 
required they should be clear.
   
   ### Issue 4: remark about not same user (root VS apisix) used depending on 
Linux distribution
   I noticed that for some Docker images, the `root`  user is used, such as 
centos.
   For others the `apisix` user is used, such as for debian.
   This could lead to different behavior since user rights are different, so 
something that would work in centos Docker image would fail in debian one.
   -> Suggestion: use applicative `apisix` in all Docker images
   Probably this issue should be created in apache/apisix-docker repository, 
but I wanted to mention it here for people who have same issues as I had. 
   Let me know if I should move it.
   
   ### Issue 5: confusing volume name in sample Kubernetes sample files
   It seems to me the volume name `apisix-admin` is confusing. In fact it 
contains the gateway routes configuration.
   It could be mistaken with something related to the Apisix admin API.
   
   See samples at 
https://github.com/apache/apisix-helm-chart/blob/master/docs/en/latest/FAQ.md#how-to-install-apache-apisix-running-in-standalone-mode
   ```
   volumes:
   [...]
   - configMap:
   name: apisix.yaml
 name: **apisix-admin**
   ```
   
   -> Suggestion: rename it, avoid `admin`. Naming proposals: `apisix-routes` 
or `apisix-routes-config` or `apisix-routes-config-yaml`
   
   
   Hope this helps !
   Thank you all Team for your good work !
   
   Sébastien


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastr

[GitHub] [apisix] uran0sH commented on issue #5453: request help: proxy-cache plugin, why the cache expiration time cannot be configured dynamically?

[GitBox]

uran0sH commented on issue #5453:
URL: https://github.com/apache/apisix/issues/5453#issuecomment-1396885215

   And I have another question: I modify the value of cache_ttl of proxy_cache 
to 1s in 'conf/default_config.yaml'. It doesn't work.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] Cheol-Soon-Choi closed issue #8712: help request: traffic-split setting

[GitBox]

Cheol-Soon-Choi closed issue #8712: help request: traffic-split setting
URL: https://github.com/apache/apisix/issues/8712


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] Cheol-Soon-Choi commented on issue #8712: help request: traffic-split setting

[GitBox]

Cheol-Soon-Choi commented on issue #8712:
URL: https://github.com/apache/apisix/issues/8712#issuecomment-1396738130

   answer is 
   
   "vars": [
   ["http_test", "IN", ["1", "3"]]
 ]
   
   thanks!


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] github-actions[bot] closed issue #3690: Support for AzureAD/OIDC integration with APISIX

[GitBox]

github-actions[bot] closed issue #3690: Support for AzureAD/OIDC integration 
with APISIX
URL: https://github.com/apache/apisix/issues/3690


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] github-actions[bot] commented on issue #3690: Support for AzureAD/OIDC integration with APISIX

[GitBox]

github-actions[bot] commented on issue #3690:
URL: https://github.com/apache/apisix/issues/3690#issuecomment-1396718990

   This issue has been closed due to lack of activity. If you think that is 
incorrect, or the issue requires additional review, you can revive the issue at 
any time.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] kellyseeme opened a new issue, #8713: when the etcd use dns ,will be some error

[GitBox]

kellyseeme opened a new issue, #8713:
URL: https://github.com/apache/apisix/issues/8713

   ### Description
   
   when the etcd connection is use domain,then in two vm cluster there one have 
some error
   `2023/01/19 11:09:53 [warn] 10007#10007: *10702332 [lua] v3.lua:716: 
request_chunk(): http://lb-etcd-03.test.com:2379: failed to parse domain: 
failed to parse domain. Retrying, context: ngx.timer
   `
   interval have 1min,10min
   
   how this happen ?the dns resolve is good ,becase another vm resolve  is ok.
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] kellyseeme commented on issue #8702: if etcd is down,the apisix not affect service?

[GitBox]

kellyseeme commented on issue #8702:
URL: https://github.com/apache/apisix/issues/8702#issuecomment-1396692532

   if etcd clsuter is down,the apisix is cache the configuretion ?if this is 
,then apisix will have the cache time,so how much time will be affect if etcd 
cluster down?


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] Cheol-Soon-Choi opened a new issue, #8712: help request: traffic-split setting

[GitBox]

Cheol-Soon-Choi opened a new issue, #8712:
URL: https://github.com/apache/apisix/issues/8712

   ### Description
   
   Referring to "https://github.com/api7/lua-resty-expr#operator-list";, 
traffic-split was set up.
   I'd appreciate it if you could check out how to use "in" in vars Attributes.
   
   ex1) response ok
 "vars": [
   ["http_test", "==", "1"]
 ]
   ex2) response ok
 "vars": [
   ["http_test", "==", "2"]
 ]
   ex3) 503 error
 "vars": [
   ["http_test", "in", "{\"1\", \"2\"}"]
 ]
   ex4) 503 error
 "vars": [
   ["http_test", "in", "{1, 2}"]
 ]
   
   Please check if there is a problem with usage.
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396640312

   I don't know what happens too. Maybe you can try to change `^/food/(.*)$` to 
`^/food/(.*)`.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396628735

   Look like APISIX still using `/food/v1/dishes` to access your upstream. Look 
like this plugin does not config correctly.


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mgonzaga1990 commented on issue #8709: help request: Setting up routing path

[GitBox]

mgonzaga1990 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396621439

   here is the access.log 
   ```
   172.20.0.1 - - [18/Jan/2023:08:59:51 +] 127.0.0.1:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.142 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.144 "http://127.0.0.1:9080";
   172.20.0.1 - - [18/Jan/2023:09:00:28 +] 127.0.0.1:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.017 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.016 "http://127.0.0.1:9080";
   172.20.0.1 - - [18/Jan/2023:09:00:32 +] 127.0.0.1:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.006 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.008 "http://127.0.0.1:9080";
   172.20.0.1 - - [18/Jan/2023:09:01:26 +] 127.0.0.1:9080 "GET /food 
HTTP/1.1" 404 47 0.000 "-" "curl/7.81.0" - - - "http://127.0.0.1:9080";
   172.20.0.1 - - [18/Jan/2023:09:01:31 +] 127.0.0.1:9080 "GET /food/ 
HTTP/1.1" 404 105 0.006 "-" "curl/7.81.0" 192.168.1.78:8090 404 0.008 
"http://127.0.0.1:9080";
   172.20.0.1 - - [18/Jan/2023:09:01:34 +] 127.0.0.1:9080 "GET /food/v1/ 
HTTP/1.1" 404 108 0.015 "-" "curl/7.81.0" 192.168.1.78:8090 404 0.016 
"http://127.0.0.1:9080";
   172.20.0.1 - - [18/Jan/2023:09:01:37 +] 127.0.0.1:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.018 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.016 "http://127.0.0.1:9080";
   172.20.0.1 - - [18/Jan/2023:09:01:56 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.014 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.012 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:03:55 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 502 154 0.000 "-" "curl/7.81.0"  - 0.000 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:04:12 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 502 154 0.000 "-" "curl/7.81.0"  - 0.000 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:04:23 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.012 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.012 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:05:18 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 200 493 0.019 "-" "curl/7.81.0" 192.168.1.78:8090 200 0.016 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:06:19 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.009 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.008 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:06:24 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 200 493 0.016 "-" "curl/7.81.0" 192.168.1.78:8090 200 0.016 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:10:12 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 200 493 0.006 "-" "curl/7.81.0" 192.168.1.78:8090 200 0.008 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:11:16 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 200 493 0.015 "-" "curl/7.81.0" 192.168.1.78:8090 200 0.012 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:25:07 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 404 47 0.000 "-" "curl/7.81.0" - - - "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:25:11 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.011 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.012 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:25:59 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.004 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.004 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:26:36 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.007 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.008 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:26:51 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.004 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.004 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:27:38 +] localhost:9080 "GET 
/food/v1/dishes HTTP/1.1" 404 114 0.009 "-" "curl/7.81.0" 192.168.1.78:8090 404 
0.008 "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:09:29:46 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 200 493 0.015 "-" "curl/7.81.0" 192.168.1.78:8090 200 0.016 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:13:02:43 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 200 493 0.428 "-" "curl/7.81.0" 192.168.1.78:8090 200 0.428 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:13:02:55 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 200 493 0.009 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:108.0) 
Gecko/20100101 Firefox/108.0" 192.168.1.78:8090 200 0.008 
"http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:13:14:21 +] localhost:9080 "GET /v1/dishes 
HTTP/1.1" 404 47 0.000 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:108.0) 
Gecko/20100101 Firefox/108.0" - - - "http://localhost:9080";
   172.20.0.1 - - [18/Jan/2023:13:14:21 +] localhost:9080 "GET /favicon.ico 
HTTP/1.1" 404 47 0.000 "http://localhost:9080/v1/dishes"; "Mozilla/5.0 (X11; 
Ubuntu; Linux x86_64; rv:108.0) Gecko/20100101 Firefox

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396620177

   Okay, Look like this is a DNS error to query httpbin.org. But that's not 
relevant to your previous question. I just want to know what path the upstream 
server receives. Httpbin will help me to look at the request message. Do you 
have any way to print the access log from your upstream server?


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mgonzaga1990 commented on issue #8709: help request: Setting up routing path

[GitBox]

mgonzaga1990 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396603017

   yeah here for the last update you wanted me to do
   
   ```
   2023/01/19 08:14:37 [error] 51#51: *458188 [lua] resolver.lua:47: 
parse_domain(): failed to parse domain: httpbin.org, error: failed to query the 
DNS server: dns server error: 5 refused, client: 172.19.0.1, server: _, 
request: "GET /food/get HTTP/1.1", host: "localhost:9080"
   2023/01/19 08:14:37 [error] 51#51: *458188 [lua] init.lua:181: 
parse_domain_for_nodes(): dns resolver domain: httpbin.org error: failed to 
query the DNS server: dns server error: 5 refused, client: 172.19.0.1, server: 
_, request: "GET /food/get HTTP/1.1", host: "localhost:9080"
   2023/01/19 08:14:37 [error] 51#51: *458188 [lua] init.lua:512: 
http_access_phase(): failed to set upstream: no valid upstream node, client: 
172.19.0.1, server: _, request: "GET /food/get HTTP/1.1", host: "localhost:9080"
   2023/01/19 08:17:55 [error] 50#50: *480654 [lua] resolver.lua:47: 
parse_domain(): failed to parse domain: httpbin.org, error: failed to query the 
DNS server: dns server error: 5 refused, client: 172.19.0.1, server: _, 
request: "GET /food/get HTTP/1.1", host: "localhost:9080"
   2023/01/19 08:17:55 [error] 50#50: *480654 [lua] init.lua:181: 
parse_domain_for_nodes(): dns resolver domain: httpbin.org error: failed to 
query the DNS server: dns server error: 5 refused, client: 172.19.0.1, server: 
_, request: "GET /food/get HTTP/1.1", host: "localhost:9080"
   2023/01/19 08:17:55 [error] 50#50: *480654 [lua] init.lua:512: 
http_access_phase(): failed to set upstream: no valid upstream node, client: 
172.19.0.1, server: _, request: "GET /food/get HTTP/1.1", host: "localhost:9080"
   ```


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396600507

   I think maybe this is not deployed APISIX right? This should happen. Do you 
see any error log in APISiX


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mgonzaga1990 commented on issue #8709: help request: Setting up routing path

[GitBox]

mgonzaga1990 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396595345

   ``` json
   {
 "uri": "/food/*",
 "name": "food-route",
 "methods": [
   "GET",
   "POST",
   "PUT",
   "DELETE",
   "PATCH",
   "HEAD",
   "OPTIONS",
   "CONNECT",
   "TRACE"
 ],
 "plugins": {
   "proxy-rewrite": {
 "regex_uri": [
   "^/food/(.*)$",
   "/$1"
 ]
   }
 },
 "upstream_id": "443902377922134721",
 "status": 1
   }
   ```
   
   ``` json
   {
 "nodes": {
   "httpbin.org": 1
 },
 "timeout": {
   "connect": 6,
   "send": 6,
   "read": 6
 },
 "type": "roundrobin",
 "scheme": "http",
 "pass_host": "pass",
 "name": "test",
 "keepalive_pool": {
   "idle_timeout": 60,
   "requests": 1000,
   "size": 320
 }
   }
   ```
   
   **result**
   
![image](https://user-images.githubusercontent.com/21145779/213389783-4669f6eb-7d4a-4d54-9574-8752c2ee87ea.png)
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mscb402 commented on issue #8709: help request: Setting up routing path

[GitBox]

mscb402 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396587217

   This is so weird. Can you can upstream the server to `httpbin.org` and 
access `/food/get` the share what returns for me?


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] mgonzaga1990 commented on issue #8709: help request: Setting up routing path

[GitBox]

mgonzaga1990 commented on issue #8709:
URL: https://github.com/apache/apisix/issues/8709#issuecomment-1396576223

   @mscb402 tried that
   
![image](https://user-images.githubusercontent.com/21145779/213386420-057f3135-8200-4be2-b47a-ec2417be7c7a.png)
   
   `
   {
 "uri": "/food/*",
 "name": "food-route",
 "methods": [
   "GET",
   "POST",
   "PUT",
   "DELETE",
   "PATCH",
   "HEAD",
   "OPTIONS",
   "CONNECT",
   "TRACE"
 ],
 "plugins": {
   "proxy-rewrite": {
 "regex_uri": [
   "^/food/(.*)$",
   "/$1"
 ]
   }
 },
 "upstream_id": "443897094827147969",
 "status": 1
   }`
   
   still getting 404
   
![image](https://user-images.githubusercontent.com/21145779/213386659-d41a36d5-a848-4e6f-b5ac-823e4388bfa7.png)
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org