notifications  

Messages by Thread

• • Re: [PR] fix: resolve env vars before YAML parsing to preserve types in standalone mode [apisix] via GitHub
  • Re: [PR] fix: resolve env vars before YAML parsing to preserve types in standalone mode [apisix] via GitHub
• Re: [I] help request: Rejected message for request-validation plugin [apisix] via GitHub
  • Re: [I] help request: Rejected message for request-validation plugin [apisix] via GitHub
• Re: [I] help request: rate limit all requests per route with `limit-conn` and `limit-req` [apisix] via GitHub
  • Re: [I] help request: rate limit all requests per route with `limit-conn` and `limit-req` [apisix] via GitHub
• Re: [I] feat: support configure multi plugin config in route [apisix] via GitHub
  • Re: [I] feat: support configure multi plugin config in route [apisix] via GitHub
• Re: [I] feat: support gRPC HTTP mapping annotation for grpc trancode plugin [apisix] via GitHub
  • Re: [I] feat: support gRPC HTTP mapping annotation for grpc trancode plugin [apisix] via GitHub
• Re: [I] help request: Integrating APISIX with External Secret Operator [apisix] via GitHub
  • Re: [I] help request: Integrating APISIX with External Secret Operator [apisix] via GitHub
• Re: [I] feat: add mTLS authentication with kubernetes apiserver [apisix] via GitHub
  • Re: [I] feat: add mTLS authentication with kubernetes apiserver [apisix] via GitHub
• Re: [I] feat: support to use plugin_config_id for Service [apisix] via GitHub
  • Re: [I] feat: support to use plugin_config_id for Service [apisix] via GitHub
• Re: [I] feat: response-rewrite plugin fine-grained cookie control [apisix] via GitHub
  • Re: [I] feat: response-rewrite plugin fine-grained cookie control [apisix] via GitHub
• Re: [I] request help: Could I use X-ID-Token header to visit the route protected by apisix openid-connect plugin [apisix] via GitHub
  • Re: [I] request help: Could I use X-ID-Token header to visit the route protected by apisix openid-connect plugin [apisix] via GitHub
• Re: [I] help request: How to create a root span while ignoring the traceparent in the request header. [apisix] via GitHub
  • Re: [I] help request: How to create a root span while ignoring the traceparent in the request header. [apisix] via GitHub
• Re: [I] feat: limit client upload rate [apisix] via GitHub
  • Re: [I] feat: limit client upload rate [apisix] via GitHub
• Re: [I] request help: in balance, set_more_retry can it be based on the response code as a condition ? [apisix] via GitHub
  • Re: [I] request help: in balance, set_more_retry can it be based on the response code as a condition ? [apisix] via GitHub
• Re: [I] feat: As a user, I want to get a specific error log message instead of 500 and a bad error log when using openid-connect plugins with the wrong redirect_uri config [apisix] via GitHub
  • Re: [I] feat: As a user, I want to get a specific error log message instead of 500 and a bad error log when using openid-connect plugins with the wrong redirect_uri config [apisix] via GitHub
• Re: [I] About kafka-logger param： batch_max_size [apisix] via GitHub
  • Re: [I] About kafka-logger param： batch_max_size [apisix] via GitHub
• Re: [I] discuss: data lost on worker shut down [apisix] via GitHub
• Re: [I] feature: Create Apache Pulsar publisher plugin [apisix] via GitHub
  • Re: [I] feature: Create Apache Pulsar publisher plugin [apisix] via GitHub
• Re: [I] feat: Add validation for admin key strength [apisix] via GitHub
  • Re: [I] feat: Add validation for admin key strength [apisix] via GitHub
• Re: [I] feat: Split timeout Field into Separate Configurations for Streaming and Non-Streaming Modes in ai-proxy-multi Plugin [apisix] via GitHub
  • Re: [I] feat: Split timeout Field into Separate Configurations for Streaming and Non-Streaming Modes in ai-proxy-multi Plugin [apisix] via GitHub
• Re: [I] feat: As a developer, I hope the schema API can export the schema of any resource [apisix] via GitHub
  • Re: [I] feat: As a developer, I hope the schema API can export the schema of any resource [apisix] via GitHub
• Re: [I] feat: As a developer, I want the `plugins/list` api can filter out any plugins with `metadata_schema` or `consumer_schema` [apisix] via GitHub
  • Re: [I] feat: As a developer, I want the `plugins/list` api can filter out any plugins with `metadata_schema` or `consumer_schema` [apisix] via GitHub
• Re: [I] feat: support AES-256-GCM algorithm to to encrypt and decrypt secret config. [apisix] via GitHub
  • Re: [I] feat: support AES-256-GCM algorithm to to encrypt and decrypt secret config. [apisix] via GitHub
• Re: [I] grpc-transcode only supports short connection, not grpc-stream, hope to add grpc-stream support [apisix] via GitHub
  • Re: [I] grpc-transcode only supports short connection, not grpc-stream, hope to add grpc-stream support [apisix] via GitHub
• Re: [I] feature: Create ActiveMQ publisher plugin [apisix] via GitHub
  • Re: [I] feature: Create ActiveMQ publisher plugin [apisix] via GitHub
• Re: [I] perf: avoid to load script for each request [apisix] via GitHub
  • Re: [I] perf: avoid to load script for each request [apisix] via GitHub
• Re: [I] feature: support rate limit in handshake phase [apisix] via GitHub
  • Re: [I] feature: support rate limit in handshake phase [apisix] via GitHub
• Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
• Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
  • Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
  • Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
  • Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
  • Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
  • Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
  • Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
  • Re: [I] bug: Regression in APISIX 3.15.0 – Routes intermittently return 404 when upstream is defined only in Service [apisix] via GitHub
• Re: [PR] feat: add native dark mode toggle to header layout [apisix-dashboard] via GitHub
  • Re: [PR] feat: add native dark mode toggle to header layout [apisix-dashboard] via GitHub
  • Re: [PR] feat: add native dark mode toggle to header layout [apisix-dashboard] via GitHub
  • Re: [PR] feat: add native dark mode toggle to header layout [apisix-dashboard] via GitHub
  • Re: [PR] feat: add native dark mode toggle to header layout [apisix-dashboard] via GitHub
• Re: [PR] feat: add global copy ID button to all resources [apisix-dashboard] via GitHub
  • Re: [PR] feat: add global copy ID button to all resources [apisix-dashboard] via GitHub
  • Re: [PR] feat: add global copy ID button to all resources [apisix-dashboard] via GitHub
  • Re: [PR] feat: add global copy ID button to all resources [apisix-dashboard] via GitHub
• Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
  • Re: [PR] refactor(ui): introduce ResourceListPage and standardize resource list [apisix-dashboard] via GitHub
• Re: [I] help request: APISIX memory usage continues to grow [apisix] via GitHub
  • Re: [I] help request: APISIX memory usage continues to grow [apisix] via GitHub
  • Re: [I] help request: APISIX memory usage continues to grow [apisix] via GitHub
• Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
  • Re: [PR] fix: use shdict instead of events module for nodes data exchange [apisix] via GitHub
• (apisix) branch dependabot/github_actions/actions/setup-node-6.3.0 deleted (was 27f2fbe9e) github-bot
• Re: [PR] chore(deps): bump actions/setup-node from 6.2.0 to 6.3.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-node from 6.2.0 to 6.3.0 [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
• Re: [PR] feat(kafka-logger): add configurable api_version for Apache Kafka 4.x support [apisix] via GitHub
  • Re: [PR] feat(kafka-logger): add configurable api_version for Apache Kafka 4.x support [apisix] via GitHub
  • Re: [PR] feat(kafka-logger): add configurable api_version for Apache Kafka 4.x support [apisix] via GitHub
  • Re: [PR] feat(kafka-logger): add configurable api_version for Apache Kafka 4.x support [apisix] via GitHub
  • Re: [PR] feat(kafka-logger): add configurable api_version for Apache Kafka 4.x support [apisix] via GitHub
• [I] bug: Apisix 3.15.0 needs anyuid [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 needs anyuid [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 needs anyuid [apisix] via GitHub
  • Re: [I] bug: Apisix 3.15.0 needs anyuid [apisix] via GitHub
• Re: [I] bug: Environment variable with common prefix returns incorrect value in init_by_lua [apisix] via GitHub
  • Re: [I] bug: Environment variable with common prefix returns incorrect value in init_by_lua [apisix] via GitHub
  • Re: [I] bug: Environment variable with common prefix returns incorrect value in init_by_lua [apisix] via GitHub
  • Re: [I] bug: Environment variable with common prefix returns incorrect value in init_by_lua [apisix] via GitHub
• Re: [PR] fix(admin): allow bidirectional format conversion for upstream.nodes in PATCH requests [apisix] via GitHub
  • Re: [PR] fix(admin): allow bidirectional format conversion for upstream.nodes in PATCH requests [apisix] via GitHub
  • Re: [PR] fix(admin): allow bidirectional format conversion for upstream.nodes in PATCH requests [apisix] via GitHub
  • Re: [PR] fix(admin): allow bidirectional format conversion for upstream.nodes in PATCH requests [apisix] via GitHub
  • Re: [PR] fix(admin): allow bidirectional format conversion for upstream.nodes in PATCH requests [apisix] via GitHub
• Re: [I] help request: stream apisix suport health check upstream? [apisix] via GitHub
  • Re: [I] help request: stream apisix suport health check upstream? [apisix] via GitHub
• Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
  • Re: [PR] GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI [apisix-dashboard] via GitHub
• Re: [I] bug: Potential etcd events lost in PR #12514 [apisix] via GitHub
  • Re: [I] bug: Potential etcd events lost in PR #12514 [apisix] via GitHub
  • Re: [I] bug: Potential etcd events lost in PR #12514 [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

• Later messages