notifications  

Messages by Thread

• • Re: [PR] fix: openid foward original id token [apisix] via GitHub
  • Re: [PR] fix: openid foward original id token [apisix] via GitHub
• Re: [I] bug: 500 Internal Server Error when querying non-existent plugin metadata via Admin API [apisix] via GitHub
• (apisix) branch master updated: fix(plugin_metadata): ensure enable_data_encryption initialization & querying issue (#12624) baoyuan
• (apisix) branch master updated: correct kafka logger sasl mechanism docs (#12725) juzhiyuan
• [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
  • Re: [PR] fix: missing trusted_addresses [apisix-helm-chart] via GitHub
• [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.10 [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.10 [apisix] via GitHub
• [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.11 [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.11 [apisix] via GitHub
• [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.12 [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.12 [apisix] via GitHub
• [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.13 [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.13 [apisix] via GitHub
• [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.14 [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.14 [apisix] via GitHub
• [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for current version [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for current version [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for current version [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for current version [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for current version [apisix] via GitHub
  • Re: [PR] docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for current version [apisix] via GitHub
• Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
• (apisix-ingress-controller) branch docs-debug updated (828d7614 -> b04acaed) traky
• [PR] docs: add configuration troubleshooting reference docs [apisix-ingress-controller] via GitHub
  • Re: [PR] docs: add configuration troubleshooting reference docs [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch docs-debug created (now 828d7614) traky
  • (apisix-ingress-controller) 01/01: troubleshoot docs traky
• (apisix-ingress-controller) branch docs-annotation updated (fd7da5ef -> 53b2d74a) traky
• Re: [I] help request: using ext-plugins on requiredBody true, memory leak occurs [apisix] via GitHub
• [PR] docs: update ingress annotation docs [apisix-ingress-controller] via GitHub
  • Re: [PR] docs: update ingress annotation docs [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch docs-annotation updated: update config.json traky
• (apisix-ingress-controller) branch docs-annotation created (now ec036442) traky
  • (apisix-ingress-controller) 01/01: update annotation docs traky
• [PR] docs: correct `kafka-logger` SASL mechanism docs [apisix] via GitHub
  • Re: [PR] docs: correct `kafka-logger` SASL mechanism docs [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: feat: support regex route for ingress annotations (#2640) ronething
• (apisix) branch master updated: fix(performance): move the ipv6 check to schema validation (#12714) nic443
• (apisix-ingress-controller) branch master updated: feat: support forward-auth for ingress annotations (#2641) ronething
• (apisix) branch master updated: docs(inspect): fix typo (#12715) wenming
• (apisix-ingress-controller) branch feat/ip-restrition deleted (was 464548dd) ronething
• (apisix-ingress-controller) branch master updated: feat: support ip restriction for ingress annotations (#2642) ronething
• Re: [I] [Site]: Fix Plugin Icons Display and Enhance Plugins Page Functionality [apisix-website] via GitHub
• [PR] Add Chinese docs for AI plugin docs [apisix] via GitHub
  • Re: [PR] docs: add chinese AI plugin docs [apisix] via GitHub
  • Re: [PR] docs: add chinese AI plugin docs [apisix] via GitHub
  • Re: [PR] docs: add chinese AI plugin docs [apisix] via GitHub
  • Re: [PR] docs: add chinese AI plugin docs [apisix] via GitHub
  • Re: [PR] docs: add chinese AI plugin docs [apisix] via GitHub
• Re: [I] docs: add Chinese docs for AI plugin docs [apisix] via GitHub
  • Re: [I] docs: add Chinese docs for AI plugin docs [apisix] via GitHub
  • Re: [I] docs: add Chinese docs for AI plugin docs [apisix] via GitHub
• (apisix-helm-chart) tag apisix-ingress-controller-1.0.7 created (now d0e5c52) github-bot
• (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
• (apisix-helm-chart) branch master updated: feat: bump apisix-ingress-controller's adc to 0.22.1 (#899) bzp2010
• [PR] feat: bump apisix-ingress-controller's adc to 0.22.1 [apisix-helm-chart] via GitHub
  • Re: [PR] feat: bump apisix-ingress-controller's adc to 0.22.1 [apisix-helm-chart] via GitHub
• [I] APISIX Graceful Shutdown for Java Plugin Runner [apisix] via GitHub
  • Re: [I] APISIX Graceful Shutdown for Plugin Runner [apisix] via GitHub
  • Re: [I] APISIX Graceful Shutdown for Plugin Runner [apisix] via GitHub
  • Re: [I] APISIX Graceful Shutdown for Plugin Runner [apisix] via GitHub
• Re: [PR] Fix image name in etcd container example [apisix-docker] via GitHub
• [I] charts.apiseven.com certificate expire [apisix-helm-chart] via GitHub
  • Re: [I] charts.apiseven.com certificate expire [apisix-helm-chart] via GitHub
  • Re: [I] charts.apiseven.com certificate expire [apisix-helm-chart] via GitHub
• (apisix-ingress-controller) branch fix-links-gateway-api deleted (was ca7345f6) traky
• (apisix-ingress-controller) branch master updated: docs: fix link to gateway api reference in doc (#2635) traky
• (apisix-website) branch master updated: Add preview staging (#1969) young
• Re: [I] help request: Using the built-in dashboard of apisix v3.14.0, I am unable to edit plugin information. [apisix-dashboard] via GitHub
  • Re: [I] help request: Using the built-in dashboard of apisix v3.14.0, I am unable to edit plugin information. [apisix-dashboard] via GitHub
  • Re: [I] help request: Using the built-in dashboard of apisix v3.14.0, I am unable to edit plugin information. [apisix-dashboard] via GitHub
  • Re: [I] help request: Using the built-in dashboard of apisix v3.14.0, I am unable to edit plugin information. [apisix-dashboard] via GitHub
  • Re: [I] help request: Using the built-in dashboard of apisix v3.14.0, I am unable to edit plugin information. [apisix-dashboard] via GitHub
• Re: [PR] fix: reloading after any node failure in eureka will lose half of the requests [apisix] via GitHub
  • Re: [PR] fix: reloading after any node failure in eureka will lose half of the requests [apisix] via GitHub
  • Re: [PR] fix: reloading after any node failure in eureka will lose half of the requests [apisix] via GitHub
  • Re: [PR] fix: reloading after any node failure in eureka will lose half of the requests [apisix] via GitHub
  • Re: [PR] fix: reloading after any node failure in eureka will lose half of the requests [apisix] via GitHub
  • Re: [PR] fix: reloading after any node failure in eureka will lose half of the requests [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: feat: support cross-namespace access service for ingress annotations (#2634) alinsran
• [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
  • Re: [I] help request: Is it feasible to use two same URIs with differnet Host? [apisix] via GitHub
• Re: [I] [Site]: Enhance code samples table with responsive design and horizontal scroll for mobile devices [apisix-website] via GitHub
  • Re: [I] [Site]: Enhance code samples table with responsive design and horizontal scroll for mobile devices [apisix-website] via GitHub
• Re: [I] docs: broken links in manage api consumers page [apisix] via GitHub
  • Re: [I] docs: broken links in manage api consumers page [apisix] via GitHub
  • Re: [I] docs: broken links in manage api consumers page [apisix] via GitHub
  • Re: [I] docs: broken links in manage api consumers page [apisix] via GitHub
  • Re: [I] docs: broken links in manage api consumers page [apisix] via GitHub
• [I] bug: Specified ectd.host from command line does'n work [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Specified ectd.host from command line does'n work [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Specified ectd.host from command line does'n work [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Specified ectd.host from command line does'n work [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Specified ectd.host from command line does'n work [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Specified ectd.host from command line does'n work [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Specified ectd.host from command line does not work [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Specified ectd.host from command line does not work [apisix-ingress-controller] via GitHub
• Re: [I] help request: openid-connect plugin X-Id-Token header contains only payload part of JWT [apisix] via GitHub
  • Re: [I] help request: openid-connect plugin X-Id-Token header contains only payload part of JWT [apisix] via GitHub
  • Re: [I] help request: openid-connect plugin X-Id-Token header contains only payload part of JWT [apisix] via GitHub
• [I] help request: How to Set `X-Forwarded-Host` and `X-Forwarded-Port` in APISIX When Using a Second Proxy? [apisix] via GitHub
  • Re: [I] help request: How to Set `X-Forwarded-Host` and `X-Forwarded-Port` in APISIX When Using a Second Proxy? [apisix] via GitHub
  • Re: [I] help request: How to Set `X-Forwarded-Host` and `X-Forwarded-Port` in APISIX When Using a Second Proxy? [apisix] via GitHub
• Re: [I] apisix dashboard - docker - panic: runtime error: invalid memory address or nil pointer dereference [apisix-dashboard] via GitHub
• Re: [I] feat: make dns resolution answers TTL configurable [apisix] via GitHub
  • Re: [I] feat: make dns resolution answers TTL configurable [apisix] via GitHub
  • Re: [I] feat: make dns resolution answers TTL configurable [apisix] via GitHub
• Re: [I] bug: The APISIX Docker installation failed since the etcd image is no longer available. [apisix] via GitHub
  • Re: [I] bug: The APISIX Docker installation failed since the etcd image is no longer available. [apisix] via GitHub
  • Re: [I] bug: The APISIX Docker installation failed since the etcd image is no longer available. [apisix] via GitHub
• [PR] fix: make protocol_name optional in mqtt-proxy plugin [apisix] via GitHub
  • Re: [PR] fix: make protocol_name optional in mqtt-proxy plugin [apisix] via GitHub
  • Re: [PR] fix: make protocol_name optional in mqtt-proxy plugin [apisix] via GitHub
  • Re: [PR] fix: make protocol_name optional in mqtt-proxy plugin [apisix] via GitHub
  • Re: [PR] fix: make protocol_name optional in mqtt-proxy plugin [apisix] via GitHub
  • Re: [PR] fix: make protocol_name optional in mqtt-proxy plugin [apisix] via GitHub
• [I] feat: As a user, I want to reference a Kubernetes Service in the GatewayProxy, so that the Service’s external IP is automatically used to populate the Gateway’s addresses field [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to reference a Kubernetes Service in the GatewayProxy, so that the Service’s external IP is automatically used to populate the Gateway’s addresses field [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to reference a Kubernetes Service in the GatewayProxy, so that the Service’s external IP is automatically used to populate the Gateway’s addresses field [apisix-ingress-controller] via GitHub
• Re: [I] help request: Running gateway in TLS mode while without terminating TLS on the gateway [apisix] via GitHub
  • Re: [I] help request: Running gateway in TLS mode while without terminating TLS on the gateway [apisix] via GitHub
  • Re: [I] help request: Running gateway in TLS mode while without terminating TLS on the gateway [apisix] via GitHub
• [I] bug: [apisix] via GitHub
  • Re: [I] bug: [apisix] via GitHub
  • Re: [I] bug: [apisix] via GitHub
  • [I] bug: [apisix] via GitHub
  • Re: [I] bug: The upstream health check is working, but it is not displayed in the "APISIX upstream check status" [apisix] via GitHub
  • [I] bug: [apisix] via GitHub
  • Re: [I] help request: request etcd endpoint timeout error [apisix] via GitHub
  • [I] bug: [apisix] via GitHub
  • Re: [I] bug: [apisix] via GitHub
  • Re: [I] bug: [apisix] via GitHub
  • Re: [I] bug: [apisix] via GitHub
  • Re: [I] help request: processing Redis during the response phase [apisix] via GitHub
  • Re: [I] help request: processing Redis during the response phase [apisix] via GitHub
  • Re: [I] help request: processing Redis during the response phase [apisix] via GitHub
• [I] Help needed, I'm testing a Python plugin and encountered error [apisix-python-plugin-runner] via GitHub
• (apisix-website) branch master updated: blog: add 2025 oct monthly report (#1970) yilialin
• [PR] feat: support ip restriction annotations for ingress [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support ip restriction for ingress annotations [apisix-ingress-controller] via GitHub
• [PR] blog: add cve-2025-62232 post [apisix-website] via GitHub
  • Re: [PR] blog: add cve-2025-62232 post [apisix-website] via GitHub
  • Re: [PR] blog: add cve-2025-62232 post [apisix-website] via GitHub
  • Re: [PR] blog: add cve-2025-62232 post [apisix-website] via GitHub
  • Re: [PR] blog: add cve-2025-62232 post [apisix-website] via GitHub
• (apisix-ingress-controller) branch feat/ip-restrition created (now 464548dd) ronething
  • (apisix-ingress-controller) 01/02: feat: support ip restriction annotations for ingress ronething
  • (apisix-ingress-controller) 02/02: fix: r ronething
• Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
• [PR] blog: add 2025 oct monthly report [apisix-website] via GitHub
  • Re: [PR] blog: add 2025 oct monthly report [apisix-website] via GitHub
• [PR] feat: support forward-auth for ingress annotations [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support forward-auth for ingress annotations [apisix-ingress-controller] via GitHub

• Earlier messages
• Later messages