notifications  

Messages by Thread

• • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
• Re: [I] 🚀 Support for k8s.apisix.apache.org/headers and rewrite-uri annotations missing in v1.8.4 [apisix-ingress-controller] via GitHub
  • Re: [I] 🚀 Support for k8s.apisix.apache.org/headers and rewrite-uri annotations missing in v1.8.4 [apisix-ingress-controller] via GitHub
  • Re: [I] 🚀 Support for k8s.apisix.apache.org/headers and rewrite-uri annotations missing in v1.8.4 [apisix-ingress-controller] via GitHub
• [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
• [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix] via GitHub
• [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
• [PR] Update common.json [apisix-dashboard] via GitHub
  • Re: [PR] Update common.json [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
• [PR] eat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
• [I] Add support Oracle OCI Vault for Secrets Mangement [apisix] via GitHub
  • Re: [I] Add support Oracle OCI Vault for Secrets Mangement [apisix] via GitHub
• [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
• [I] change of etcd.image.registry triggers ERROR [apisix-helm-chart] via GitHub
  • Re: [I] change of etcd.image.registry triggers ERROR [apisix-helm-chart] via GitHub
• [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
• [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
  • Re: [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
  • Re: [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
  • Re: [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: feat: support deployment of multiple data plane modes (#2647) alinsran
• (apisix-dashboard) branch master updated: feat: add Turkish (tr) language support (#3252) baoyuan
• [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
• [PR] Feature/ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
• Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix] via GitHub
  • Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix] via GitHub
  • Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix] via GitHub
  • Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix] via GitHub
• Re: [I] help request: remote_addr is error [apisix] via GitHub
• [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
  • Re: [PR] test: add stream route E2E tests with detail page flows [apisix-dashboard] via GitHub
• Re: [I] Test(resource): services [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): services [apisix-dashboard] via GitHub
• [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): add comprehensive service CRUD tests and UI utility functions [apisix-dashboard] via GitHub
• [PR] test(services): add E2E tests for list page and CRUD operations [apisix-dashboard] via GitHub
  • Re: [PR] test(services): add E2E tests for list page and CRUD operations [apisix-dashboard] via GitHub
• Re: [I] request help: why the location in response header that returned by APISIX has the 9443 port? [apisix] via GitHub
  • Re: [I] request help: why the location in response header that returned by APISIX has the 9443 port? [apisix] via GitHub
  • Re: [I] request help: why the location in response header that returned by APISIX has the 9443 port? [apisix] via GitHub
• [PR] feat: add configurable real_ip_header option for nginx [apisix-helm-chart] via GitHub
  • Re: [PR] feat: add configurable real_ip_header option for nginx [apisix-helm-chart] via GitHub
  • Re: [PR] feat: add configurable real_ip_header option for nginx [apisix-helm-chart] via GitHub
  • Re: [PR] feat: add configurable real_ip_header option for nginx [apisix-helm-chart] via GitHub
  • Re: [PR] feat: add configurable real_ip_header option for nginx [apisix-helm-chart] via GitHub
• [I] help request: When upstream return 302, I want to return client follow 302 and return 200.How can i configure? [apisix] via GitHub
  • Re: [I] help request: When upstream return 302, I want to return client follow 302 and return 200.How can i configure? [apisix] via GitHub
  • Re: [I] help request: When upstream return 302, I want to return client follow 302 and return 200.How can i configure? [apisix] via GitHub
  • Re: [I] help request: When upstream return 302, I want to return client follow 302 and return 200.How can i configure? [apisix] via GitHub
• (apisix-ingress-controller) branch fix/au-unknow deleted (was 4cd81dd4) bzp2010
• (apisix-ingress-controller) branch master updated: fix(ApisixUpstream): cannot recognize kind (#2622) bzp2010
• [PR] docs: replace link to `config-default.yaml` [apisix-helm-chart] via GitHub
  • Re: [PR] docs: replace links to `config-default.yaml` [apisix-helm-chart] via GitHub
• (apisix-helm-chart) branch docs-update-default-links created (now 4e5ec13) traky
  • (apisix-helm-chart) 01/01: replace link to config-default.yaml traky
• (apisix-ingress-controller) branch bzp/fix-au-status-updater-kind-unknown deleted (was a5783ae8) bzp2010
• [PR] fix: status updater prints the kind of ApisixUpstream as unknown [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: status updater prints the kind of ApisixUpstream as unknown [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: status updater prints the kind of ApisixUpstream as unknown [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: status updater prints the kind of ApisixUpstream as unknown [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch bzp/fix-au-status-updater-kind-unknown created (now a5783ae8) bzp2010
  • (apisix-ingress-controller) 01/01: fix: status updater prints the kind of ApisixUpstream as unknown bzp2010
• Re: [I] request help: Gateway API upstream returning 400 error with HTML response [apisix-ingress-controller] via GitHub
• Re: [I] help request: no GatewayProxy configs provided [apisix-ingress-controller] via GitHub
• Re: [I] bug: Ingress controller not creating upstream on ApisixUpstream resource creation [apisix-ingress-controller] via GitHub
• [I] bug: the Admin API Key in GatewayProxy is missing certain validity checks [apisix-ingress-controller] via GitHub
• [I] Make configMap in customPlugins Optional [apisix-helm-chart] via GitHub
• Re: [PR] feat: Add proxy-chain plugin to chain multiple upstream service calls [apisix] via GitHub
  • Re: [PR] feat: Add proxy-chain plugin to chain multiple upstream service calls [apisix] via GitHub
• [I] Feature request: Adaptive Local Rate Limiting (Auto-Aware of APISIX Cluster Size) [apisix] via GitHub
  • Re: [I] Feature request: Adaptive Local Rate Limiting (Auto-Aware of APISIX Cluster Size) [apisix] via GitHub
  • Re: [I] Feature request: Adaptive Local Rate Limiting (Auto-Aware of APISIX Cluster Size) [apisix] via GitHub
  • Re: [I] Feature request: Adaptive Local Rate Limiting (Auto-Aware of APISIX Cluster Size) [apisix] via GitHub
  • Re: [I] Feature request: Adaptive Local Rate Limiting (Auto-Aware of APISIX Cluster Size) [apisix] via GitHub
  • Re: [I] Feature request: Adaptive Local Rate Limiting (Auto-Aware of APISIX Cluster Size) [apisix] via GitHub
  • Re: [I] Feature request: Adaptive Local Rate Limiting (Auto-Aware of APISIX Cluster Size) [apisix] via GitHub
• Re: [I] request help: create stream route to proxy to TLS over TCP upstream [apisix-ingress-controller] via GitHub
  • Re: [I] request help: create stream route to proxy to TLS over TCP upstream [apisix-ingress-controller] via GitHub
  • Re: [I] request help: create stream route to proxy to TLS over TCP upstream [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch docs-annotation deleted (was 53b2d74a) juzhiyuan
• (apisix-ingress-controller) branch master updated: docs: update ingress annotation docs (#2645) juzhiyuan

• Earlier messages
• Later messages