notifications  

Messages by Thread

• • Re: [I] bug: HTTP2 protocol not working when ApisixUpstream scheme is set to https [apisix] via GitHub
• [I] request help: How are the version numbers of APISIX Ingress Controller and the Apache APISIX gateway (Admin API) correspondence? [apisix-ingress-controller] via GitHub
  • Re: [I] request help: How are the version numbers of APISIX Ingress Controller and the Apache APISIX gateway (Admin API) correspondence? [apisix-ingress-controller] via GitHub
  • Re: [I] request help: How are the version numbers of APISIX Ingress Controller and the Apache APISIX gateway (Admin API) correspondence? [apisix-ingress-controller] via GitHub
• [I] help request: Does the latest version of Apache APISIX Dashboard support Chinese? If so, how to set it up? [apisix-dashboard] via GitHub
  • Re: [I] help request: Does the latest version of Apache APISIX Dashboard support Chinese? If so, how to set it up? [apisix-dashboard] via GitHub
  • Re: [I] help request: Does the latest version of Apache APISIX Dashboard support Chinese? If so, how to set it up? [apisix-dashboard] via GitHub
  • Re: [I] help request: Does the latest version of Apache APISIX Dashboard support Chinese? If so, how to set it up? [apisix-dashboard] via GitHub
• Re: [I] help request: upstream with eureka discovery got no host allowed while connecting to upstream! [apisix] via GitHub
• (apisix) branch master updated: feat(eureka): allow domain named nodes (#12993) baoyuan
• (apisix) branch master updated (7186888b8 -> cfa15d779) baoyuan
• [I] help request: 如何给每个授权配置插件limit-count [apisix] via GitHub
  • Re: [I] help request: 如何给每个授权配置插件limit-count [apisix] via GitHub
  • Re: [I] help request: 如何给每个授权配置插件limit-count [apisix] via GitHub
  • Re: [I] help request: how to configure plugin limit-count for each authorized plugin [apisix] via GitHub
  • Re: [I] help request: how to configure plugin limit-count for each authorized plugin [apisix] via GitHub
• (apisix) branch master updated: fix: remove redundant field for rate limit plugins (#12959) baoyuan
• [PR] feat: enhance rate limiting rules support [apisix] via GitHub
  • Re: [PR] feat: support rules in limit-conn and ai-rate-limiting [apisix] via GitHub
  • Re: [PR] feat: support rules in limit-conn and ai-rate-limiting [apisix] via GitHub
• [I] help request: Some pods in APISIX are experiencing a "404 Route not found" exception [apisix] via GitHub
  • Re: [I] help request: Some pods in APISIX are experiencing a "404 Route not found" exception [apisix] via GitHub
  • Re: [I] help request: Some pods in APISIX are experiencing a "404 Route not found" exception [apisix] via GitHub
  • Re: [I] help request: Some pods in APISIX are experiencing a "404 Route not found" exception [apisix] via GitHub
  • Re: [I] help request: Some pods in APISIX are experiencing a "404 Route not found" exception [apisix] via GitHub
• Re: [PR] chore: optimize debian-dev Dockerfiles for better layer caching [apisix-docker] via GitHub
  • Re: [PR] chore: optimize debian-dev Dockerfiles for better layer caching [apisix-docker] via GitHub
  • Re: [PR] chore: optimize debian-dev Dockerfiles for better layer caching [apisix-docker] via GitHub
• [PR] fix(plugin): merge consumer group plugins when consumer has no direct plugins [apisix] via GitHub
  • Re: [PR] fix(plugin): merge consumer group plugins when consumer has no direct plugins [apisix] via GitHub
  • Re: [PR] fix(plugin): merge consumer group plugins when consumer has no direct plugins [apisix] via GitHub
  • Re: [PR] fix(plugin): merge consumer group plugins when consumer has no direct plugins [apisix] via GitHub
  • Re: [PR] fix(plugin): merge consumer group plugins when consumer has no direct plugins [apisix] via GitHub
• (apisix) branch master updated: feat(openidc): support redis for session storage (#12986) shreemaanabhishek
• [I] feat: As a user, I want to add metadata to routes, so that I can filter global plugins configuration by _meta.filter with this metadata [apisix] via GitHub
  • Re: [I] feat: As a user, I want to add metadata to routes, so that I can filter global plugins configuration by _meta.filter with this metadata [apisix] via GitHub
  • Re: [I] feat: As a user, I want to add metadata to routes, so that I can filter global plugins configuration by _meta.filter with this metadata [apisix] via GitHub
• [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
  • Re: [PR] feat: allow fetching stream healthcheck data through control api [apisix] via GitHub
• [I] feat: As a user, I want to store basic auth credentials in hashed form, to not leak them to authorized admins [apisix] via GitHub
  • Re: [I] feat: As a user, I want to store basic auth credentials in hashed form, to not leak them to authorized admins [apisix] via GitHub
  • Re: [I] feat: As a user, I want to store basic auth credentials in hashed form, to not leak them to authorized admins [apisix] via GitHub
  • Re: [I] feat: As a user, I want to store basic auth credentials in hashed form, to not leak them to authorized admins [apisix] via GitHub
• [PR] feat: support authentication via headers [apisix] via GitHub
  • Re: [PR] feat: support authentication via headers [apisix] via GitHub
  • Re: [PR] feat: support authentication via headers [apisix] via GitHub
  • Re: [PR] feat: support authentication via headers [apisix] via GitHub
  • Re: [PR] feat: support authentication via headers [apisix] via GitHub
  • Re: [PR] feat: support authentication via headers [apisix] via GitHub
• [I] 修复切换语言报错 [apisix-dashboard] via GitHub
  • Re: [I] 修复切换语言报错 [apisix-dashboard] via GitHub
  • Re: [I] 修复切换语言报错 [apisix-dashboard] via GitHub
  • Re: [I] bug: crash after switching languages [apisix-dashboard] via GitHub
  • Re: [I] bug: crash after switching languages [apisix-dashboard] via GitHub
  • Re: [I] bug: crash after switching languages [apisix-dashboard] via GitHub
  • Re: [I] bug: crash after switching languages [apisix-dashboard] via GitHub
• (apisix-dashboard) branch dependabot/github_actions/apache/skywalking-eyes-0630b017b4e34f27f0d8719c873d703fb31ec8de deleted (was 906b54a59) github-bot
• [PR] chore(deps): bump apache/skywalking-eyes from 55373684d1b70e5f8fd9fc8ec114a89ad11a56a3 to 1a2a5024a0d5937db21af5dbc57cf73f0ac1de8f [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 55373684d1b70e5f8fd9fc8ec114a89ad11a56a3 to 1a2a5024a0d5937db21af5dbc57cf73f0ac1de8f [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 55373684d1b70e5f8fd9fc8ec114a89ad11a56a3 to 1a2a5024a0d5937db21af5dbc57cf73f0ac1de8f [apisix-dashboard] via GitHub
• (apisix) branch master updated: feat(limit-count): support configuring multiple rules (#12977) shreemaanabhishek
• [PR] feat(eureka): allow domain named nodes [apisix] via GitHub
  • Re: [PR] feat(eureka): allow domain named nodes [apisix] via GitHub
  • Re: [PR] feat(eureka): allow domain named nodes [apisix] via GitHub
  • Re: [PR] feat(eureka): allow domain named nodes [apisix] via GitHub
• [I] help request: Does the latest version of Apache APISIX Dashboard support Chinese? If so, how to set it up? [apisix] via GitHub
• [I] Does the latest version support Chinese? If so, how to set it up? [apisix-dashboard] via GitHub
  • Re: [I] Does the latest version support Chinese? If so, how to set it up? [apisix-dashboard] via GitHub
• (apisix) branch master updated: chore: add ngx.flush after ngx.print (#1194) (#12988) nic443
• [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
  • Re: [PR] feat(balancer): add traffic warm-up (slow start) support for upstream nodes [apisix] via GitHub
• [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
  • Re: [PR] fix(opentelemetry): validate x-request-id before using it as trace_id [apisix] via GitHub
• [I] bug: Apisix 3.15.0 tries to connect to etcd in standalone api-driven mode (non crashing) [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 tries to connect to etcd in standalone api-driven mode (non crashing) [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 tries to connect to etcd in standalone api-driven mode (non crashing) [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 tries to connect to etcd in standalone api-driven mode (non crashing) [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 tries to connect to etcd in standalone api-driven mode (non crashing) [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 tries to connect to etcd in standalone api-driven mode (non crashing) [apisix] via GitHub
• Re: [I] help request: memory growing up [apisix] via GitHub
• (apisix) branch master updated: doc fix (#12958) yilialin
• [I] feat: As a user, I want the ingress controller to set `status.loadBalancer.ingress` on an ingress, so that I can see if the ingress is healthy from the ArgoCD dashboard [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want the ingress controller to set `status.loadBalancer.ingress` on an ingress, so that I can see if the ingress is healthy from the ArgoCD dashboard [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want the ingress controller to set `status.loadBalancer.ingress` on an ingress, so that I can see if the ingress is healthy from the ArgoCD dashboard [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want the ingress controller to set `status.loadBalancer.ingress` on an ingress, so that I can see if the ingress is healthy from the ArgoCD dashboard [apisix-ingress-controller] via GitHub
• (apisix-website) branch master updated: blog: add 3.15.0 release notes (#1982) traky
• [PR] chore: add ngx.flush after ngx.print [apisix] via GitHub
  • Re: [PR] chore: add ngx.flush after ngx.print [apisix] via GitHub
• Re: [PR] feat: add plugin execution tracing to OpenTelemetry plugin [apisix] via GitHub
  • Re: [PR] feat: add plugin execution tracing to OpenTelemetry plugin [apisix] via GitHub
• Re: [I] request help: How to configure mTLS between ingress controller and apisix control plane [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: feat: add more spans to opentelemetry plugin (#12686) nic443
• [PR] fix: DNS upstream healthcheck recreation with IP changes [apisix] via GitHub
  • Re: [PR] fix: DNS upstream healthcheck recreation with IP changes [apisix] via GitHub
• [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
  • Re: [PR] feat(openidc): support redis for session storage [apisix] via GitHub
• [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
  • Re: [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
• [PR] Update version of dependency lua-casbin to 1.46.0 [apisix] via GitHub
  • Re: [PR] Update version of dependency lua-casbin to 1.46.0 [apisix] via GitHub
  • Re: [PR] chore: update version of dependency lua-casbin to 1.46.0 [apisix] via GitHub
  • Re: [PR] chore: update version of dependency lua-casbin to 1.46.0 [apisix] via GitHub
• [I] feat: As a user, I want to the kafka-logger plugin support Apache Kafka 4.x [apisix] via GitHub
  • Re: [I] feat: As a user, I want the kafka-logger plugin supports Apache Kafka 4.x [apisix] via GitHub
  • Re: [I] feat: As a user, I want the kafka-logger plugin supports Apache Kafka 4.x [apisix] via GitHub
  • Re: [I] feat: As a user, I want the kafka-logger plugin supports Apache Kafka 4.x [apisix] via GitHub
• (apisix-helm-chart) tag apisix-2.13.0 created (now 9d5ad2a) github-bot
• (apisix-helm-chart) branch master updated: chore: upgrade apisix to 3.15.0 (#938) shreemaanabhishek
• [I] What's going on with this project? [apisix-dashboard] via GitHub
  • Re: [I] What's going on with this project? [apisix-dashboard] via GitHub
• [PR] chore: upgrade apisix to 3.15.0 [apisix-helm-chart] via GitHub
  • Re: [PR] chore: upgrade apisix to 3.15.0 [apisix-helm-chart] via GitHub
• [I] Help Request: ApisixTls certificates not syncing - HTTPS fails with 'failed to match any SSL certificate by SNI' [apisix-ingress-controller] via GitHub
  • Re: [I] Help Request: ApisixTls certificates not syncing - HTTPS fails with 'failed to match any SSL certificate by SNI' [apisix-ingress-controller] via GitHub
  • Re: [I] Help Request: ApisixTls certificates not syncing - HTTPS fails with 'failed to match any SSL certificate by SNI' [apisix-ingress-controller] via GitHub
  • Re: [I] Help Request: ApisixTls certificates not syncing - HTTPS fails with 'failed to match any SSL certificate by SNI' [apisix-ingress-controller] via GitHub
  • Re: [I] Help Request: ApisixTls certificates not syncing - HTTPS fails with 'failed to match any SSL certificate by SNI' [apisix-ingress-controller] via GitHub
• [I] help request: the ApisixRoute resource does not create route [apisix-ingress-controller] via GitHub
  • Re: [I] help request: the ApisixRoute resource does not create route [apisix-ingress-controller] via GitHub
  • Re: [I] help request: the ApisixRoute resource does not create route [apisix-ingress-controller] via GitHub
• (apisix-docker) branch master updated: chore: release 3.15.0 (#613) shreemaanabhishek
• (apisix-docker) branch release/apisix-3.15.0 created (now 642c074) shreemaanabhishek
• [I] help request: the ApisixRoute resource does not create route [apisix] via GitHub
• (apisix) branch dependabot/github_actions/actions/setup-go-6.2.0 created (now 7fa7e28f3) github-bot
• [PR] chore(deps): bump actions/setup-go from 5.6.0 to 6.2.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-go from 5.6.0 to 6.2.0 [apisix] via GitHub
• [PR] chore(deps): bump actions/checkout from 5.0.1 to 6.0.2 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 5.0.1 to 6.0.2 [apisix] via GitHub
• (apisix) branch dependabot/github_actions/actions/checkout-6.0.2 created (now 0ab099408) github-bot
• (apisix) branch dependabot/github_actions/actions/github-script-8.0.0 created (now b0c47dcc9) github-bot
• (apisix) branch dependabot/github_actions/actions/stale-10.1.1 created (now 5665311aa) github-bot
• [PR] chore(deps): bump actions/github-script from 7.1.0 to 8.0.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/github-script from 7.1.0 to 8.0.0 [apisix] via GitHub
• [PR] chore(deps): bump actions/stale from 8.0.0 to 10.1.1 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/stale from 8.0.0 to 10.1.1 [apisix] via GitHub
• (apisix-website) branch master updated: docs: release APISIX v3.15.0 (#1986) shreemaanabhishek
• [PR] chore: release 3.15.0 [apisix-docker] via GitHub
  • Re: [PR] chore: release 3.15.0 [apisix-docker] via GitHub
• (apisix) branch master updated: chore(deps-dev): bump @modelcontextprotocol/sdk in /t (#12971) baoyuan
• (apisix) branch dependabot/npm_and_yarn/t/modelcontextprotocol/sdk-1.26.0 deleted (was b211465b8) baoyuan
• [I] help request: The route was not successfully created. [apisix] via GitHub
  • Re: [I] help request: The route was not successfully created. [apisix] via GitHub
  • Re: [I] help request: The route was not successfully created. [apisix] via GitHub
  • Re: [I] help request: The route was not successfully created. [apisix] via GitHub
• (apisix) branch master updated: feat(jwt): support more algorithms (#12944) nic443
• [PR] docs: release APISIX v3.15.0 [apisix-website] via GitHub
  • Re: [PR] docs: release APISIX v3.15.0 [apisix-website] via GitHub
• (apisix) branch master updated: chore: release 3.15.0 (#12947) shreemaanabhishek
• (apisix) tag 3.15.0 created (now cd0e1fab2) shreemaanabhishek
• [I] zOneOf validation errors when exactly one field is provided [apisix-dashboard] via GitHub
  • Re: [I] zOneOf validation errors when exactly one field is provided [apisix-dashboard] via GitHub
  • Re: [I] zOneOf validation errors when exactly one field is provided [apisix-dashboard] via GitHub
  • Re: [I] zOneOf validation errors when exactly one field is provided [apisix-dashboard] via GitHub
  • Re: [I] zOneOf validation errors when exactly one field is provided [apisix-dashboard] via GitHub
• (apisix) branch master updated: fix: control api return wrong status data for passive health check (#12975) nic443
• [PR] feat(limit-count): support configuring multiple rules [apisix] via GitHub

• Earlier messages
• Later messages