notifications  

Messages by Thread

• • Re: [I] bug: authz-keycloak should omit querystring, so that keycloak authorization works [apisix] via GitHub
  • Re: [I] bug: authz-keycloak should omit querystring, so that keycloak authorization works [apisix] via GitHub
  • Re: [I] bug: authz-keycloak should omit querystring, so that keycloak authorization works [apisix] via GitHub
• Re: [I] bug: golang plugin fails to get big body [apisix] via GitHub
• [I] request help: What is the recommended way to proxy TCP traffic for Services in other namespaces? [apisix-ingress-controller] via GitHub
  • Re: [I] request help: What is the recommended way to proxy TCP traffic for Services in other namespaces? [apisix-ingress-controller] via GitHub
  • Re: [I] request help: What is the recommended way to proxy TCP traffic for Services in other namespaces? [apisix-ingress-controller] via GitHub
  • Re: [I] request help: What is the recommended way to proxy TCP traffic for Services in other namespaces? [apisix-ingress-controller] via GitHub
  • Re: [I] request help: What is the recommended way to proxy TCP traffic for Services in other namespaces? [apisix-ingress-controller] via GitHub
• [PR] fix: elasticsearch-logger plugin support elasticsaerch data_stream [apisix] via GitHub
  • Re: [PR] fix: elasticsearch-logger plugin support elasticsaerch data_stream [apisix] via GitHub
• Re: [I] Who is using APISIX ingress controller？（欢迎使用 APISIX ingress controller 的个人和公司在此留言） [apisix-ingress-controller] via GitHub
  • Re: [I] Who is using APISIX ingress controller？（欢迎使用 APISIX ingress controller 的个人和公司在此留言） [apisix-ingress-controller] via GitHub
• Re: [I] feat: As a user, I want to check the subordinate relationship in the Admin API [apisix] via GitHub
  • Re: [I] feat: As a user, I want to check the subordinate relationship in the Admin API [apisix] via GitHub
• [I] bug: AIC does not discover default GatewayProxy [apisix-ingress-controller] via GitHub
  • Re: [I] bug: AIC does not discover default GatewayProxy [apisix-ingress-controller] via GitHub
  • Re: [I] bug: AIC does not discover default GatewayProxy [apisix-ingress-controller] via GitHub
  • Re: [I] bug: AIC does not discover default GatewayProxy [apisix-ingress-controller] via GitHub
  • Re: [I] bug: AIC does not discover default GatewayProxy [apisix-ingress-controller] via GitHub
  • Re: [I] bug: AIC does not discover default GatewayProxy [apisix-ingress-controller] via GitHub
  • Re: [I] bug: AIC does not discover default GatewayProxy [apisix-ingress-controller] via GitHub
• [I] bug: Verification of upstream TLS certificates for L4 (stream) protocols is not performed [apisix] via GitHub
  • Re: [I] bug: Verification of upstream TLS certificates for L4 (stream) protocols is not performed [apisix] via GitHub
• [PR] enhance toc scrolling accuracy [apisix-dashboard] via GitHub
  • Re: [PR] enhance toc scrolling accuracy [apisix-dashboard] via GitHub
• [I] TOC navigation scrolls to incorrect position [apisix-dashboard] via GitHub
  • Re: [I] TOC navigation scrolls to incorrect position [apisix-dashboard] via GitHub
• [I] request help: To understand why the admin api might be creating the username as namespace_consumername [apisix-ingress-controller] via GitHub
  • Re: [I] request help: To understand why the admin api might be creating the username as namespace_consumername [apisix-ingress-controller] via GitHub
  • Re: [I] request help: To understand why the admin api might be creating the username as namespace_consumername [apisix-ingress-controller] via GitHub
  • Re: [I] request help: To understand why the admin api might be creating the username as namespace_consumername [apisix-ingress-controller] via GitHub
  • Re: [I] request help: To understand why the admin api might be creating the username as namespace_consumername [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch docs-update-rsc-support deleted (was cc9ded53) traky
• (apisix-ingress-controller) branch master updated: docs: remove allowedRoutes from unsupported resource (#2659) traky
• [I] help request: Secrets gcp integration error [apisix] via GitHub
  • Re: [I] help request: Secrets gcp integration error [apisix] via GitHub
  • Re: [I] help request: Secrets gcp integration error [apisix] via GitHub
  • Re: [I] help request: Secrets gcp integration error [apisix] via GitHub
• Re: [PR] fix: correct pre/post hook typos in Kubernetes discovery and improve cleanup safety [apisix] via GitHub
  • Re: [PR] fix: correct pre/post hook typos in Kubernetes discovery and improve cleanup safety [apisix] via GitHub
  • Re: [PR] fix: correct pre/post hook typos in Kubernetes discovery and improve cleanup safety [apisix] via GitHub
  • Re: [PR] fix: correct pre/post hook typos in Kubernetes discovery and improve cleanup safety [apisix] via GitHub
  • Re: [PR] fix: correct pre/post hook typos in Kubernetes discovery and improve cleanup safety [apisix] via GitHub
• [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Standalone API-driven mode + Gateway API: TCPRoute / stream proxy does not work [apisix-ingress-controller] via GitHub
• [PR] Patch 141 [apisix-ingress-controller] via GitHub
  • Re: [PR] Patch 141 [apisix-ingress-controller] via GitHub
• [PR] feat: support benchmark test [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support benchmark test [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support benchmark test [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support benchmark test [apisix-ingress-controller] via GitHub
• Re: [I] feat: As a user, I want to know if V3.2 is still an LTS version. If not, what are some alternatives for those who are using V3.2? [apisix] via GitHub
  • Re: [I] feat: As a user, I want to know if V3.2 is still an LTS version. If not, what are some alternatives for those who are using V3.2? [apisix] via GitHub
  • Re: [I] feat: As a user, I want to know if V3.2 is still an LTS version. If not, what are some alternatives for those who are using V3.2? [apisix] via GitHub
• [I] bug: http-logger Request Body is Empty [apisix] via GitHub
  • Re: [I] bug: http-logger Request Body is Empty [apisix] via GitHub
  • Re: [I] bug: http-logger Request Body is Empty [apisix] via GitHub
  • Re: [I] bug: http-logger Request Body is Empty [apisix] via GitHub
  • Re: [I] bug: http-logger Request Body is Empty [apisix] via GitHub
  • Re: [I] bug: http-logger Request Body is Empty [apisix] via GitHub
  • Re: [I] bug: http-logger Request Body is Empty [apisix] via GitHub
  • Re: [I] bug: http-logger Request Body is Empty [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: docs: add configuration troubleshooting reference docs (#2646) traky
• (apisix-ingress-controller) branch docs-debug updated (b04acaed -> d87da72c) traky
• (apisix-ingress-controller) branch docs-debug deleted (was d87da72c) traky
• (apisix-ingress-controller) branch master updated: docs: update ApisixRoute stream support and fix typo (#2662) juzhiyuan
• (apisix-ingress-controller) branch docs-minor-fix deleted (was 795aa312) juzhiyuan
• (apisix-ingress-controller) branch docs-minor-fix updated (ee5a3968 -> 795aa312) traky
• (apisix-ingress-controller) branch docs-minor-fix updated (79be0a56 -> ee5a3968) traky
• [PR] docs(getting-started): fix '502 Bad Gateway' error in the getting sta… [apisix] via GitHub
  • Re: [PR] docs(getting-started): fix '502 Bad Gateway' error in the getting sta… [apisix] via GitHub
  • Re: [PR] docs(getting-started): fix '502 Bad Gateway' error in the getting sta… [apisix] via GitHub
  • Re: [PR] docs(getting-started): fix '502 Bad Gateway' error in the getting sta… [apisix] via GitHub
  • Re: [PR] docs(getting-started): fix '502 Bad Gateway' error in the getting sta… [apisix] via GitHub
• Re: [I] Bug Report: APISIX Standalone API-driven Mode Workers Not Ready on Startup [apisix-helm-chart] via GitHub
• [PR] batch-request: the number of sub responses does not match the number of sub requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub responses does not match the number of sub requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub responses does not match the number of sub requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub responses does not match the number of sub requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
  • Re: [PR] fix(batch-requests): the number of sub-responses does not match that of sub-requests [apisix] via GitHub
• Re: [PR] chore(deps): Update lua-resty-openidc version from 1.7.6-3 to 1.8.0-1 and lua-resty-session version from 3.10 to 4.0.5-1 [apisix] via GitHub
  • Re: [PR] chore(deps): Update lua-resty-openidc version from 1.7.6-3 to 1.8.0-1 and lua-resty-session version from 3.10 to 4.0.5-1 [apisix] via GitHub
  • Re: [PR] chore(deps): Update lua-resty-openidc version from 1.7.6-3 to 1.8.0-1 and lua-resty-session version from 3.10 to 4.0.5-1 [apisix] via GitHub
  • Re: [PR] chore(deps): Update lua-resty-openidc version from 1.7.6-3 to 1.8.0-1 and lua-resty-session version from 3.10 to 4.0.5-1 [apisix] via GitHub
  • Re: [PR] chore(deps): Update lua-resty-openidc version from 1.7.6-3 to 1.8.0-1 and lua-resty-session version from 3.10 to 4.0.5-1 [apisix] via GitHub
  • Re: [PR] chore(deps): Update lua-resty-openidc version from 1.7.6-3 to 1.8.0-1 and lua-resty-session version from 3.10 to 4.0.5-1 [apisix] via GitHub
• [PR] docs: fix typo in sentence [apisix-ingress-controller] via GitHub
  • Re: [PR] docs: update ApisixRoute stream support and fix typo [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch docs-minor-fix created (now 79be0a56) traky
  • (apisix-ingress-controller) 01/01: typo traky
• Re: [I] request help: I want to check in ext-plugin-post-resp plugin according to upstream response status. [apisix-java-plugin-runner] via GitHub
• (apisix-dashboard) branch dependabot/github_actions/actions/checkout-6 deleted (was 09bcec8f6) github-bot
• (apisix-dashboard) branch master updated: chore(deps): bump actions/checkout from 5 to 6 (#3260) young
• [I] help request: Can i split the log files by Route ID? [apisix] via GitHub
  • Re: [I] help request: Can i split the log files by Route ID? [apisix] via GitHub
  • Re: [I] help request: Can i split the log files by Route ID? [apisix] via GitHub
  • Re: [I] help request: Can i split the log files by Route ID? [apisix] via GitHub
  • Re: [I] help request: Can i split the log files by Route ID? [apisix] via GitHub
• (apisix-helm-chart) tag apisix-2.12.4 created (now bdfe0b7) github-bot
• (apisix-helm-chart) branch master updated: feat: add trusted_addresses option to apisix configmap template (#909) baoyuan
• [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
  • Re: [PR] Add trusted_addresses option to apisix configmap template [apisix-helm-chart] via GitHub
• Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
  • Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
  • Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
  • Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
  • Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
  • Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
  • Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
  • Re: [I] Support JSONSchema to Form UI [apisix-dashboard] via GitHub
• Re: [PR] feat: add PROXY protocol support [apisix-helm-chart] via GitHub
  • Re: [PR] feat: add PROXY protocol support [apisix-helm-chart] via GitHub
• [PR] feat(debug): add print_traceback for debugging [apisix] via GitHub
  • Re: [PR] feat(debug): add print_traceback for debugging [apisix] via GitHub
• (apisix) branch master updated: feat: add validate API to standalone mode (#12718) baoyuan
• [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
  • Re: [I] help request: Malformed encoding found in chunked-encoding returned [apisix] via GitHub
• [I] help request: Using Environment Variables in APISIX Routes [apisix] via GitHub
  • Re: [I] help request: Using Environment Variables in APISIX Routes [apisix] via GitHub
  • Re: [I] help request: Using Environment Variables in APISIX Routes [apisix] via GitHub
• [I] bug: Unable to override values lua_shared_dict prometheus-metrics and lua_shared_dict prometheus-cache [apisix] via GitHub
  • Re: [I] bug: Unable to override values lua_shared_dict prometheus-metrics and lua_shared_dict prometheus-cache [apisix] via GitHub
  • Re: [I] bug: Unable to override values lua_shared_dict prometheus-metrics and lua_shared_dict prometheus-cache [apisix] via GitHub
  • Re: [I] bug: Unable to override values lua_shared_dict prometheus-metrics and lua_shared_dict prometheus-cache [apisix] via GitHub
  • Re: [I] bug: Unable to override values lua_shared_dict prometheus-metrics and lua_shared_dict prometheus-cache [apisix] via GitHub
  • Re: [I] bug: Unable to override values lua_shared_dict prometheus-metrics and lua_shared_dict prometheus-cache [apisix] via GitHub
  • Re: [I] bug: Unable to override values lua_shared_dict prometheus-metrics and lua_shared_dict prometheus-cache [apisix] via GitHub
• [PR] fix: change consul event to shared dict [apisix] via GitHub
  • Re: [PR] fix: change consul event module to shared dict [apisix] via GitHub
• (apisix) branch dependabot/github_actions/actions/checkout-6 deleted (was 6080625a5) github-bot
• [PR] feat: Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
  • Re: [PR] feat(disvocery): Add zookeeper discovery [apisix] via GitHub
• [I] bug: attempt to index field 'upstream' (a string value) [apisix] via GitHub
  • Re: [I] bug: attempt to index field 'upstream' (a string value) [apisix] via GitHub
  • Re: [I] bug: attempt to index field 'upstream' (a string value) [apisix] via GitHub
  • Re: [I] bug: attempt to index field 'upstream' (a string value) [apisix] via GitHub
  • Re: [I] bug: attempt to index field 'upstream' (a string value) [apisix] via GitHub
  • Re: [I] bug: attempt to index field 'upstream' (a string value) [apisix] via GitHub
  • Re: [I] bug: attempt to index field 'upstream' (a string value) [apisix] via GitHub
• (apisix-dashboard) branch dependabot/github_actions/actions/checkout-6 updated (93404b1dc -> 09bcec8f6) github-bot
• (apisix-dashboard) branch master updated: chore(deps): bump apache/skywalking-eyes (#3261) baoyuan
• (apisix-dashboard) branch dependabot/github_actions/apache/skywalking-eyes-b7f8b351c2db8005972712d7efc0a15484a15bcb deleted (was 412195869) baoyuan
• [I] Why hasn't the initw_worker method been executed? [apisix] via GitHub
  • Re: [I] Why hasn't the initw_worker method been executed? [apisix] via GitHub
  • Re: [I] Why hasn't the initw_worker method been executed? [apisix] via GitHub
  • Re: [I] Why hasn't the initw_worker method been executed? [apisix] via GitHub
• [I] bug: event worker failed: failed to receive the header , attempt to index upvalue 'ev' (a nil value) [apisix] via GitHub
  • Re: [I] bug: event worker failed: failed to receive the header , attempt to index upvalue 'ev' (a nil value) [apisix] via GitHub
  • Re: [I] bug: event worker failed: failed to receive the header , attempt to index upvalue 'ev' (a nil value) [apisix] via GitHub
  • Re: [I] bug: event worker failed: failed to receive the header , attempt to index upvalue 'ev' (a nil value) [apisix] via GitHub
  • Re: [I] bug: event worker failed: failed to receive the header , attempt to index upvalue 'ev' (a nil value) [apisix] via GitHub

• Earlier messages
• Later messages