notifications  

Messages by Thread

• • 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
• [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: [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: [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
• [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
• [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
• (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] 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
• [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
• [I] bug: Datadog issue on egress size metric in K8s [apisix] via GitHub
  • Re: [I] bug: Datadog issue on egress size metric in K8s [apisix] via GitHub
  • Re: [I] bug: Datadog issue on egress size metric in K8s [apisix] via GitHub
• Re: [I] bug: nginx proxy_redirect no default setting [apisix] via GitHub
  • Re: [I] bug: nginx proxy_redirect no default setting [apisix] via GitHub
• Re: [I] help request: The Kafka logger plugin in Apisix occasionally obtains an empty response body [apisix] via GitHub
  • Re: [I] help request: The Kafka logger plugin in Apisix occasionally obtains an empty response body [apisix] via GitHub
• [I] Bug: Use the Go custom plug-in to end the RPC call abnormally in the response stage, exit the plug-in call sequence in the response stage, and return the response directly [apisix-go-plugin-runner] via GitHub
• (apisix) branch release/3.13 updated: docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.13 (#12729) traky
• (apisix) branch release/3.12 updated: docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.12 (#12730) traky
• apisix.git: Error while running github feature from release/3.12:.asf.yaml Apache Infrastructure
• Re: [I] help request: "400 Request Header Or Cookie Too Large" [apisix] via GitHub
  • Re: [I] help request: "400 Request Header Or Cookie Too Large" [apisix] via GitHub
  • Re: [I] help request: "400 Request Header Or Cookie Too Large" [apisix] via GitHub
• Re: [I] help request: I have created custom kafka plugin to send proper JSON data to Kafka consumer from Apisix API but API is not connecting to Kafka brokers [apisix] via GitHub
  • Re: [I] help request: I have created custom kafka plugin to send proper JSON data to Kafka consumer from Apisix API but API is not connecting to Kafka brokers [apisix] via GitHub
• Re: [I] help request: Websocket service receives RST packet from Apisix Pods during Node Termination [apisix] via GitHub
  • Re: [I] help request: Websocket service receives RST packet from Apisix Pods during Node Termination [apisix] via GitHub
• Re: [I] bug: OPA plugin - invalid OPA decision format - err: `result` field does not exist [apisix] via GitHub
• (apisix) branch release/3.14 updated: docs(zh): add missing tutorials (manage-api-consumers, cache-api-response) for release/3.14 (#12728) traky
• [I] secret "apisix-etcd-jwt-token" not found [apisix-helm-chart] via GitHub
• [I] help request: Is the support for the Kubernetes Gateway API in the latest GA release (1.8) of the apisix-ingress-controller still not GA-ready? If not, are there any plans for it in the future? [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Is the support for the Kubernetes Gateway API in the latest GA release (1.8) of the apisix-ingress-controller still not GA-ready? If not, are there any plans for it in the future? [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Is the support for the Kubernetes Gateway API in the latest GA release (1.8) of the apisix-ingress-controller still not GA-ready? If not, are there any plans for it in the future? [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Is the support for the Kubernetes Gateway API in the latest GA release (1.8) of the apisix-ingress-controller still not GA-ready? If not, are there any plans for it in the future? [apisix-ingress-controller] via GitHub
• Re: [I] help request: How to define keepalive through ApisixUpstream_ The idle of the pool_ Timeout [apisix-ingress-controller] via GitHub
  • Re: [I] help request: How to define keepalive through ApisixUpstream_ The idle of the pool_ Timeout [apisix-ingress-controller] via GitHub
  • Re: [I] help request: How to define keepalive through ApisixUpstream_ The idle of the pool_ Timeout [apisix-ingress-controller] via GitHub
• [PR] feat: add Turkish (tr) language support [apisix-dashboard] via GitHub
  • Re: [PR] feat: add Turkish (tr) language support [apisix-dashboard] via GitHub
• [PR] Fix/mask sensitive fields [apisix-dashboard] via GitHub
  • Re: [PR] Fix/mask sensitive fields [apisix-dashboard] via GitHub
  • Re: [PR] Fix/mask sensitive fields [apisix-dashboard] via GitHub
  • Re: [PR] Fix/mask sensitive fields [apisix-dashboard] via GitHub
  • Re: [PR] Fix/mask sensitive fields [apisix-dashboard] via GitHub
  • Re: [PR] fix: mask sensitive fields [apisix-dashboard] via GitHub
• [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
  • Re: [I] help request: Custom plugin failed to load subdirectories module [apisix] via GitHub
• (apisix-ingress-controller) branch docs-repo deleted (was a5f41cf0) traky
• (apisix-ingress-controller) branch master updated: docs: update apisix ingress controller docs helm repo (#2649) traky
• Re: [I] help request: 3.2.1 memory leak [apisix] via GitHub
• Re: [I] help request: memory growing up [apisix] via GitHub
• [PR] docs: update apisix ingress controller docs helm repo [apisix-ingress-controller] via GitHub
  • Re: [PR] docs: update apisix ingress controller docs helm repo [apisix-ingress-controller] via GitHub
• (apisix-helm-chart) branch gh-pages updated: change repo url traky
• (apisix-ingress-controller) branch docs-repo created (now a5f41cf0) traky
  • (apisix-ingress-controller) 01/01: change aic helm repo traky
• Re: [I] APISIX Dashboard Tests [apisix-dashboard] via GitHub
  • Re: [I] APISIX Dashboard Tests [apisix-dashboard] via GitHub
• [I] help request: Is the support for the Kubernetes Gateway API in the latest GA release (1.8) of the apisix-ingress-controller still not GA-ready? If not, are there any plans for it in the future? [apisix] via GitHub
• Re: [I] Test(resource): consumer groups [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): consumer groups [apisix-dashboard] via GitHub
• [PR] test: add E2E tests for Consumer Groups (#3086) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for Consumer Groups (#3086) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for Consumer Groups (#3086) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for Consumer Groups [apisix-dashboard] via GitHub
• Re: [I] Test(resource): ssls [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): ssls [apisix-dashboard] via GitHub
• [PR] test: add E2E tests for SSLs (#3087) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for SSLs (#3087) [apisix-dashboard] via GitHub
• [I] upstream resolve domain is empty [apisix] via GitHub
  • Re: [I] upstream resolve domain is empty [apisix] via GitHub
  • Re: [I] upstream resolve domain is empty [apisix] via GitHub
  • Re: [I] upstream resolve domain is empty [apisix] via GitHub
• [I] [Site]: 404 when clicking on ingress-controller from docs page. [apisix-website] via GitHub
  • Re: [I] [Site]: 404 when clicking on ingress-controller from docs page. [apisix-website] via GitHub
• [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
• [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
• Re: [I] Hope "forward auth" can set cache time，and, Options requests can be approved [apisix] via GitHub
• [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
  • Re: [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
  • [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
  • Re: [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
• [I] help request: Dynamic Upstream Routing [apisix] via GitHub
  • Re: [I] help request: Dynamic Upstream Routing [apisix] via GitHub
  • Re: [I] help request: Dynamic Upstream Routing [apisix] via GitHub

• Earlier messages
• Later messages