Web This site Trusted
30 result(s) for “okapi bm25 site terms com pp site github com site plugins grace org site github com site:apache.org” of 172 matched · page 3 · 1171 ms
Scope: Nishi’s own index (our crawl + Common Crawl) — not the whole live web. Some sites block all automated crawlers (anti-bot walls), so their pages may be absent here even though we never filter lawful content.
Freshness: newest result fetched 23 d ago · median age of these results 23 d · 28 of 30 carry a fetch time
https://apisix.apache.org/docs/apisix/plugins/body-transformer/
org/soap/envelope/">
<soap-env:Body>
<ns0:getCountryRequest xmlns:ns0="http://spring
https://apisix.apache.org/docs/apisix/plugins/jwt-auth/
base64_secret
lifetime_grace_period>=0Grace period in seconds
https://maven.apache.org
Upcoming: How to migrate plugins to the new Maven 4 API
https://apisix.apache.org/docs/apisix/terminology/plugin-config/
NOTE
If a Route already has the plugins field configured, the plugins in the Plugin Config will effectively be merged to it
https://apisix.apache.org/docs/apisix/plugins/consumer-restriction/
The Plugin needs to work with authentication plugins, such as key-auth and jwt-auth, which means you should always create at least one Consumer in your use case
https://apisix.apache.org/docs/apisix/plugins/serverless/
These plugins enable the execution of user-defined logic at the beginning and end of the execution phases the functions hook to
https://apisix.apache.org/docs/apisix/plugins/workflow/
Learn More
Docs
Description
The workflow Plugin supports the conditional execution of user-defined actions to client traffic based on a given set of rules, defined using lua-resty-expr. This provides a granular approach to traffic
https://apisix.apache.org/docs/apisix/plugins/mqtt-proxy/
yaml
INFO
Attaching L4 plugins is currently not supported with Gateway API
https://apisix.apache.org/docs/apisix/plugins/key-auth/
Learn More
Docs
Description
The key-auth Plugin supports the use of an authentication key as a mechanism for clients to authenticate themselves before accessing Upstream resources.
To use the Plugin, you would configure authentication
https://apisix.apache.org/docs/apisix/plugins/acl/
It checks consumer labels (from APISIX Consumers) or external user attributes (from authentication plugins that set ctx
https://any23.apache.org/
Previous versions are available from the Apache Archives site
https://apisix.apache.org/docs/apisix/plugins/jwe-decrypt/
yaml
APISIX Ingress Controller
ApisixConsumer only supports authentication plugins via the authParameter field, and jwe-decrypt is not among the supported types
https://apisix.apache.org/docs/apisix/plugins/cors/
com"} is set in the Plugin metadata, then ["EXAMPLE"] can be used to allow CORS on the origin https://example
https://apisix.apache.org/docs/apisix/plugins/data-mask/
Learn More
Docs
Description
The data-mask Plugin masks or redacts sensitive fields in request data — query parameters, headers, and body — before they appear in access logs or logger plugins (such as file-logger or http-logger).
This
https://apisix.apache.org/docs/apisix/plugins/ai-prompt-template/
yaml
Gateway API
Create a Route with the ai-prompt-template and ai-proxy Plugins
https://apisix.apache.org/docs/apisix/plugins/response-rewrite/
exit in the access or rewrite phases from other plugins
https://apisix.apache.org/docs/apisix/plugin-develop/
For instance:
plugins: # See `conf/config
https://apisix.apache.org/docs/apisix/plugins/ldap-auth-advanced/
Attributes
TrueDN of the LDAP user bound to this Consumer, for example cn=Jane Doe,ou=users,dc=example,dc=org
https://forrest.apache.org/
Much effort has gone into making the process of generating a new site easy and simple:
Step 1: Do 'forrest seed' to populate the directory with template site structure and contents
https://apisix.apache.org/docs/apisix/plugins/limit-req/
Learn More
Docs
Description
The limit-req Plugin uses the leaky bucket algorithm to rate limit the number of the requests and allow for throttling.
Local vs Redis Rate Limiting
The limit-req Plugin supports two modes of rate limiting:
https://apisix.apache.org/docs/apisix/plugins/request-id/
Learn More
Docs
Description
The request-id Plugin assigns a unique ID to each request proxied through the gateway, which can be used for request tracking and debugging. If a request already includes an ID in the header specified by
https://cwiki.apache.org/confluence/s/d41d8cd98f00b204e9800998ecf8427e-CDN/-cig8sa/9116/n2r6gc/9b591fc0a6b4c60a86e7408cc35216f2/_/download/contextbatch/css/atl.confluence.plugins.pagetree-desktop,main,space,atl.general,-_super/batch.css?analytics-enabled=true&hostenabled=true&theme.switcher=true
pagetree:pagetree-css-resources', location = 'com/atlassian/confluence/plugins/pagetree/resource/css/pagetree
https://apisix.apache.org/docs/apisix/terminology/upstream/
Learn More
Docs
Description
Upstream is a virtual host abstraction that performs load balancing on a given set of service nodes according to the configured rules.
Although Upstream can be directly configured to the Route or Service, using
https://apisix.apache.org/docs/apisix/plugins/opa/
Learn More
Docs
Description
The opa Plugin supports the integration with Open Policy Agent (OPA), a unified policy engine and framework that helps define and enforce authorization policies. Authorization logic is defined in Rego and
https://apisix.apache.org/docs/apisix/plugins/dubbo-proxy/
Learn More
Docs
IMPORTANT
If you are using OpenResty, you need to build it with Dubbo support. See How do I build the APISIX runtime environment for details.
Runtime Attributes
Dubbo provider service method.
Enable Plugin
conf/config.yaml
https://apisix.apache.org/docs/apisix/tutorials/protect-api/
NOTE
If Route, Service, Plugin Config or Consumer are all bound to the same for plugins, only one plugin configuration will take effect
https://apisix.apache.org/docs/apisix/getting-started/README/
It provides dynamic routing, load balancing, authentication, rate limiting, observability, and 100+ plugins for managing API traffic at scale
https://apisix.apache.org/docs/apisix/tutorials/manage-api-consumers/
Consumer concept is extremely useful when you have different consumers requesting the same API and you need to execute various Plugins and Upstream configurations based on the consumer
https://apisix.apache.org/
The same gateway, now for your LLM traffic
Proxy, secure, and govern traffic to documented LLM providers and OpenAI-compatible endpoints with the plugins and observability you already use for APIs
https://apisix.apache.org/docs/apisix/plugins/proxy-mirror/
Learn More
Docs
Description
The proxy-mirror Plugin duplicates ingress traffic to APISIX and forwards them to a designated upstream, without interrupting the regular services. You can configure the Plugin to mirror all traffic or only a