do with route2's
> > vars.
> >
> >
> > *ZhengSong Tu*
> > My GitHub: https://github.com/tzssangglass
> > Apache APISIX: https://github.com/apache/apisix
> >
> > Li Yang 于2021年11月23日周二 下午4:01写道：
> > >
> > > Hi ZhengSong,
> > >
u
wrote:
> hi, yang.
>
> > Route X should be matched first if and only if route X's matching
> > rule set is a proper superset of route Y's matching rule set.*
>
> I have doubts about this, can you show some example?
>
> *ZhengSong Tu*
> My Gi
Hello, Community,
Currently in APISIX, there is a built-in prioritization of routes by
the matching uri.
For example, if the requested uri is /foo/bar, and the server side routes
contain /foo/bar and /foo/* and /*.
Although all 3 uri patterns match /foo/bar, only the exact match /foo/bar
wi
Hi Jatinder,
You can check the access log and the remote address will show you what
the IP address APISIX got from the request.
If the IP is what you expect, try debugging this:
1. See whether there is one or more nodes between the APISIX and your
request client.
2. Check real_ip_module, it's pos
and can only be discovered at
> runtime, which is a hidden danger of development.
>
> Thanks,
> Ming Wen, Apache APISIX PMC Chair
> Twitter: _WenMing
>
>
> Li Yang 于2021年9月9日周四 下午5:48写道：
>
> > Hey mates,
> >
> > Apache APISIX has an official plugin limit-c
Hey mates,
Apache APISIX has an official plugin limit-conn, and from the document
there is one line stated: "Key can be customized by the user, only
need to modify a line of code of the plug-in to complete. It is a
security consideration that is not open in the plugin."
What is the security conce
The tile is misleading, it might be multi config center instead of
multi data center.
I'm trying to clarify a little first, so after this feature is developed,
APISIX will be able to read configs not only from ETCD, but
from any config server as long as we have created adaptor
between config cente
> So, we can use the `consul_kv` below:
>
> ```bash
> --- apisix_yaml
> routes:
> -
>uri: /*
>upstream:
> service_name: http://127.0.0.1:8500/v1/kv/upstreams/webpages/
> discovery_type: consul_kv
> type: roundrobin
> ```
>
> And, we don't need to
It sounds like a very useful feature for me.
My question is how will we configure routes after this feature?
Is this your planned way of configuring routes?
--- apisix_yaml
routes:
-
uri: /*
upstream:
service_name: http://127.0.0.1:8500/v1/kv/upstreams/webpages/
discovery_t
