notifications  

Messages by Thread

• • Re: [I] bug: Difference between ADC and APISIX schemas regarding secrets in client CA for upstream mTLS [apisix] via GitHub
  • Re: [I] bug: Difference between ADC and APISIX schemas regarding secrets in client CA for upstream mTLS [apisix] via GitHub
  • Re: [I] bug: Difference between ADC and APISIX schemas regarding secrets in client CA for upstream mTLS [apisix] via GitHub
• [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
  • Re: [PR] fix(limit-req): use parent resource key for consumer isolation [apisix] via GitHub
• Re: [I] feat: Apisix Prometheus metrics - Disable unneeded labels/metrics [apisix] via GitHub
• [I] APISIX Ingress Controller chart version mismatch [apisix-helm-chart] via GitHub
• [I] Please update the ConfigMap template to make it easier to read. [apisix-helm-chart] via GitHub
• Re: [I] bug: casbin plugin returning intermittent 403 error [apisix] via GitHub
• [I] Support ssl_trusted_certificate and conditional sni in deployment.etcd.tls configuration [apisix-helm-chart] via GitHub
• [PR] Set upstream and upstream_latency vars in ext-plugin-post-resp for logging [apisix] via GitHub
  • Re: [PR] fix: Set upstream and upstream_latency vars in ext-plugin-post-resp for logging [apisix] via GitHub
  • Re: [PR] fix: Set upstream and upstream_latency vars in ext-plugin-post-resp for logging [apisix] via GitHub
  • Re: [PR] fix: Set upstream and upstream_latency vars in ext-plugin-post-resp for logging [apisix] via GitHub
  • Re: [PR] fix: Set upstream and upstream_latency vars in ext-plugin-post-resp for logging [apisix] via GitHub
• Re: [PR] fix: disallow creating duplicate plugins in global rules [apisix] via GitHub
  • Re: [PR] fix: disallow creating duplicate plugins in global rules [apisix] via GitHub
• Re: [PR] APISIX and APISIX-ingress containers to work without anyuid SCC [apisix-docker] via GitHub
  • Re: [PR] APISIX and APISIX-ingress containers to work without anyuid SCC [apisix-docker] via GitHub
  • Re: [PR] APISIX and APISIX-ingress containers to work without anyuid SCC [apisix-docker] via GitHub
• (apisix) branch dependabot/github_actions/actions/stale-10.2.0 created (now e6da22a56) github-bot
• [PR] chore(deps): bump actions/stale from 10.1.1 to 10.2.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/stale from 10.1.1 to 10.2.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/stale from 10.1.1 to 10.2.0 [apisix] via GitHub
• [PR] chore(deps): bump peaceiris/actions-gh-pages from 3.9.0 to 4.0.0 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump peaceiris/actions-gh-pages from 3.9.0 to 4.0.0 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump peaceiris/actions-gh-pages from 3.9.0 to 4.0.0 [apisix-website] via GitHub
• (apisix-website) branch dependabot/github_actions/peaceiris/actions-gh-pages-4.0.0 created (now d5d57fe6316) github-bot
• [I] bug: Some nginx vars related to upstream are missing when using ext-plugin-post-resp [apisix] via GitHub
  • Re: [I] bug: Some nginx vars related to upstream are missing when using ext-plugin-post-resp [apisix] via GitHub
  • Re: [I] bug: Some nginx vars related to upstream are missing when using ext-plugin-post-resp [apisix] via GitHub
  • Re: [I] bug: Some nginx vars related to upstream are missing when using ext-plugin-post-resp [apisix] via GitHub
• [I] bug: Header values modified by ext-plugin-pre-req/ext-plugin-post-req not applied in ext-plugin-post-resp [apisix] via GitHub
  • Re: [I] bug: Header values modified by ext-plugin-pre-req/ext-plugin-post-req not applied in ext-plugin-post-resp [apisix] via GitHub
  • Re: [I] bug: Header values modified by ext-plugin-pre-req/ext-plugin-post-req not applied in ext-plugin-post-resp [apisix] via GitHub
  • Re: [I] bug: Header values modified by ext-plugin-pre-req/ext-plugin-post-req not applied in ext-plugin-post-resp [apisix] via GitHub
• Re: [I] feat: add max request and response body size attributes to http-logger plugin [apisix] via GitHub
  • Re: [I] feat: add max request and response body size attributes to http-logger plugin [apisix] via GitHub
• [PR] Fix IndexOutOfBoundsException when calling PostRequest.getUpstreamHeaders [apisix-java-plugin-runner] via GitHub
  • Re: [PR] Fix IndexOutOfBoundsException when calling PostRequest.getUpstreamHeaders [apisix-java-plugin-runner] via GitHub
• Re: [I] bug: Control API does not return health check data (RC5 in standalone mode) [apisix-ingress-controller] via GitHub
• [PR] fix: add secrets support to ssl by id in upstream mtls config [apisix] via GitHub
  • Re: [PR] fix: add secrets support to ssl by id in upstream mtls config [apisix] via GitHub
  • Re: [PR] fix: add secrets support to ssl by id in upstream mtls config [apisix] via GitHub
  • Re: [PR] fix: add secrets support to ssl by id in upstream mtls config [apisix] via GitHub
• Re: [PR] Fix: Add missing empty spaces in exit / die message for invalid certificate path [apisix] via GitHub
• [I] Add extraEnvFrom helm option [apisix-helm-chart] via GitHub
• (apisix-website) branch dependabot/github_actions/actions/setup-node-6 created (now 3950c6bd57b) github-bot
• [PR] chore(deps): bump actions/setup-python from 4.1.0 to 6.2.0 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-python from 4.1.0 to 6.2.0 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-python from 4.1.0 to 6.2.0 [apisix-website] via GitHub
• [PR] chore(deps): bump actions/cache from 3 to 5 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/cache from 3 to 5 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/cache from 3 to 5 [apisix-website] via GitHub
• Re: [PR] chore(deps): bump actions/setup-python from 4.1.0 to 4.7.1 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-python from 4.1.0 to 4.7.1 [apisix-website] via GitHub
• (apisix-website) branch dependabot/github_actions/actions/setup-node-4 deleted (was 32172e03064) github-bot
• (apisix-website) branch dependabot/github_actions/actions/checkout-4.1.1 deleted (was 8a3c01ad0fe) github-bot
• (apisix-website) branch dependabot/github_actions/actions/setup-python-4.7.1 deleted (was 5896588ce41) github-bot
• Re: [PR] chore(deps): bump actions/setup-node from 3 to 4 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-node from 3 to 4 [apisix-website] via GitHub
• [PR] chore(deps): bump actions/setup-node from 3 to 6 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-node from 3 to 6 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-node from 3 to 6 [apisix-website] via GitHub
• (apisix-website) branch dependabot/github_actions/actions/setup-python-6.2.0 created (now 3614af4e3f8) github-bot
• [PR] chore(deps): bump actions/checkout from 3.1.0 to 6.0.2 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 3.1.0 to 6.0.2 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 3.1.0 to 6.0.2 [apisix-website] via GitHub
• (apisix-website) branch dependabot/github_actions/actions/cache-5 created (now 99fe4df02a8) github-bot
• (apisix-website) branch dependabot/github_actions/actions/checkout-6.0.2 created (now 44fbc7a53eb) github-bot
• Re: [PR] chore(deps): bump actions/checkout from 3.1.0 to 4.1.1 [apisix-website] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 3.1.0 to 4.1.1 [apisix-website] via GitHub
• Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
  • Re: [PR] fix: preserve plugins with empty config using targeted approach [apisix-dashboard] via GitHub
• Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] 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
  • 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
• Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
• [PR] chore(deps): bump qs from 6.14.1 to 6.14.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump qs from 6.14.1 to 6.14.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump qs from 6.14.1 to 6.14.2 [apisix-dashboard] via GitHub
• (apisix-dashboard) branch dependabot/npm_and_yarn/qs-6.14.2 created (now 130943dcd) github-bot
• Re: [PR] feat: Enhanced hero section background visibility and comprehensive mobile responsive design #1961 [apisix-website] via GitHub
  • Re: [PR] feat: Enhanced hero section background visibility and comprehensive mobile responsive design #1961 [apisix-website] via GitHub
• Re: [PR] Fix: Improve plugin icons rendering and responsiveness on Plugins Page #1963 [apisix-website] via GitHub
  • Re: [PR] Fix: Improve plugin icons rendering and responsiveness on Plugins Page #1963 [apisix-website] via GitHub
• Re: [PR] Fix: Enhance code samples table with responsive design and horizontal scroll for mobile devices #1965 [apisix-website] via GitHub
  • Re: [PR] Fix: Enhance code samples table with responsive design and horizontal scroll for mobile devices #1965 [apisix-website] via GitHub
• (apisix-website) branch dependabot/npm_and_yarn/axios-1.6.0 deleted (was fdbfb34f5ad) github-bot
• Re: [I] [Site]: UI & Mobile Responsiveness Improvements [apisix-website] via GitHub
• Re: [PR] chore(deps-dev): bump axios from 0.21.4 to 1.6.0 [apisix-website] via GitHub
  • Re: [PR] chore(deps-dev): bump axios from 0.21.4 to 1.6.0 [apisix-website] via GitHub
• Re: [PR] fix: Fixed the vertical scroll bar on the home page [apisix-website] via GitHub
• Re: [I] [Site]: Missing theme toggle switch on website pages [apisix-website] via GitHub
  • Re: [I] [Site]: Missing theme toggle switch on website pages [apisix-website] 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: [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] 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] help request: upstream related header is missing when using external plugins [apisix] via GitHub
• Re: [PR] Added proxy protocol support settings [apisix-helm-chart] via GitHub
• Re: [PR] fix: relax frontend validation for multi-auth plugin [apisix-dashboard] 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
• [I] bug: nginx env variable for private key is not resolved in upstream with mtls [apisix] via GitHub
  • Re: [I] bug: nginx env variable for private key is not resolved in upstream with mtls [apisix] via GitHub
  • Re: [I] bug: nginx env variable for private key is not resolved in upstream with mtls [apisix] via GitHub
  • Re: [I] bug: nginx env variable for private key is not resolved in upstream with mtls [apisix] via GitHub
  • Re: [I] bug: nginx env variable for private key is not resolved in upstream with mtls [apisix] via GitHub
  • Re: [I] bug: nginx env variable for private key is not resolved in upstream with mtls [apisix] via GitHub
  • Re: [I] bug: nginx env variable for private key is not resolved in upstream with mtls [apisix] via GitHub
  • Re: [I] bug: nginx env variable for private key is not resolved in upstream with mtls [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] ci: add explicit least permissions to workflows [apisix] via GitHub
  • Re: [PR] ci: add explicit least permissions to workflows [apisix] via GitHub
  • Re: [PR] ci: add explicit least permissions to workflows [apisix] via GitHub
• [PR] Fix wording for Script and Plugin compatibility [apisix] via GitHub
  • Re: [PR] docs: fix wording for Script and Plugin compatibility [apisix] via GitHub
  • Re: [PR] docs: fix wording for Script and Plugin compatibility [apisix] via GitHub
  • Re: [PR] docs: fix wording for Script and Plugin compatibility [apisix] via GitHub

• Earlier messages
• Later messages