Skip to main content

Biweekly Report (Sep 13 - Sep 30)

· 3 min read

From 9.13 to 9.30, 32 developers have committed 93 commits to Apache APISIX. Thank you to these folks for making the Apache APISIX project better with your selfless efforts!


Apache APISIX has grown as a community since the first day of open source and has quickly become the most active open source API gateway project in the world. These achievements could not have been achieved without the joint efforts of our community partners.

"The Apache APISIX Community Weekly Newsletter hopes to help community members better grasp the weekly progress of the Apache APISIX community and facilitate your participation in the Apache APISIX community.

We've also put together some issues for those new to the community!

Contributor statistics

This week's contributor list
Click to Preview

New contributors this week
Click to Preview

Good first issue

Issue #5080


Problem Description: Previously the upstream service used IP authentication and the actual client IP was obtained from the x-forwarded-for request header. Now I need to change to gateway HMAC authentication, so I need to block upstream IP authentication through the gateway. Tried to modify x-forwarded-for via the proxy rewrite plugin, but it did not work: !

Screenshot of problem description
Click to Preview

Issue #5108


problem description: as follows, when enabling the request validation plugin on a route:" delete "

curl -H 'X-API-KEY: xxxxxxxxxxxxxxxxxxx' -X PUT -d '
"type": "object",
"type": "string"
"type": "number"
"service_name": "PRODUCTSSERVICE",
"type": "roundrobin",
"discovery_type": "eureka"

Test it with the following command:

$ curl -X POST -d '{"product-Name":"Laptop","pri-ce":12345.00}'

Get the following default message.

property "price" is required

Feature highlights of the week