ISIX PMC Chair
> Twitter: _WenMing
>
>
> Jan Li 于2020年11月30日周一 下午7:41写道：
>
> > No, it should not make config.yaml too complicated. And please consider
> > what it brings to us, it enables us to use apisix dynamic features along
> > with any flavor of nginx configurati
need to change for the proxy protocol server
On Wed, Nov 25, 2020 at 1:19 PM YuanSheng Wang wrote:
> On Tue, Nov 24, 2020 at 7:20 PM Jan Li wrote:
>
> > For example,
> >
> > You want apisix to listen on 4 ports:
> >
> >- 80 for http
> >-
nce in this scenario
the real_ip_header should only be bound to the listening port.
On Tue, Nov 24, 2020 at 6:14 PM YuanSheng Wang wrote:
> @Jan Li
>
> Can you provide some examples? I think the community needs them for
> understanding.
>
>
> On Tue, Nov 24, 2020 at
Hi community,
APISIX is using config file and apisix bin file to generate nginx
config file.
This provides APISIX the capability of overriding nginx's default
configurations, but also introduces some problems:
1. There is only one nginx server which supports the dynamic features of
I think enhancing documentation should be a long-term strategy for the
community.
Documents should not be too much, but they need to be maintained like we
maintain code.
For every pull request, if some documents get out-of-date, they should be
updated in the same pull request. Maybe we should rem
Hi community,
Currently APISIX uses Redis to do cluster-level rate limit, it calls
Redis for every request to check whether the rate control is broken.
Problem is that Redis becomes an important dependency in the critical
path of request processing. So if Redis is under maintenance, e
e PRs and issues
> every month.
> I think we can consider hosting an Apache APISIX DevCon to encourage
> developers to exchange experiences. What do you think?
>
> Thanks,
> Ming Wen, Apache APISIX & Apache SkyWalking
> Twitter: _WenMing
>
--
Jan Li
Senior Software En
t;
> > Support adding GraphQL field to route matching conditions.
> >
> > For example:
> >
> > ```shell
> > curl http://127.0.0.1:9080/apisix/admin/routes/1 -X PUT -i -d '
> > {
> > "uri": "/graphql",
> > "va
Hi team,
I'm using Prometheus plugin to monitor status code, but there is an
obstacle when we try to group status code by URI.
Suppose we have such a route configuration:
{"uri": "/event/*", vars: [["uri", "~~", "^/event/.*/subscribe"]]}
And the actual request uri ca
Hi team,
When using APISIX in critical env, we'd like it fail fast to avoid
false healthy server which cannot process any actual requests:
1. If APISIX cannot connect to ETCD when it's configured with the
ETCD config center, it means pre-configured routes are not available. At
this po
Thanks YuanSheng.
On Fri, Mar 27, 2020 at 11:13 AM YuanSheng Wang wrote:
> > Is this correct?
>
> yes, you are right.
>
> match step:
> 1. fully matching
> 2. prefix matching: Sort by prefix length, longer matches first
>
> On Fri, Mar 27, 2020 at 10:20 AM
Hi team,
Could you please help me confirm the priority of route matching?
Especially when multiple routes include wildcards.
For example, I have 3 routes configured:
/foo/bar
/foo/*
/*
I suppose the behavior is like this:
/foo/bar will mat
Vote for option 1, and I think we can check the version in *apisix ini**t* and
report error if version is incompatible.
On Wed, Mar 11, 2020 at 8:16 PM YuanSheng Wang wrote:
> Hi:
>
> Apache APISIX users use a different version of `conf/config.yaml`,
> this caused the service to fail to start.
>
you can check conf/config.yaml
On Tue, Mar 10, 2020 at 6:01 PM 奔波虫 <2562957...@qq.com> wrote:
> Dear all，
>
>
>
> I have an etcd cluster.
> How to use the cluster in apisix?
>
>
>
>
> yours，
>
> Ben
--
[image: Airwallex]
*Jan Li*
ggestions are welcome, and you are welcome to join the release work.
>
> Thanks!
>
--
[image: Airwallex]
*Jan Li*
Senior Software Engineer
+8615316315503
jan...@airwallex.com [image: Airwallex] <https://www.airwallex.com/>
Room 1802, 18th Floor, Tower A, China Overseas In
15 matches
Mail list logo
