Skip to main content

Biweekly Report｜11.15-11.30 Feature Highlights Update in Progress

· 4 min read

From 11.15 to 11.30, 37 contributors submitted 87 commits for Apache APISIX. Thank you all for your contributions to Apache APISIX. It is your selfless contribution to make the Apache APISIX project better!

Introduction#

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

"If you want to go fast, go alone.If you want to go far, go together." The Apache APISIX Community Weekly Report hopes to help community members better understand the weekly progress of the Apache APISIX community and and facilitate everyone to participate in the Apache APISIX community.

We have also compiled some issues suitable for newcomers to the community to participate in! If you are interested, don't miss it!

Contributor Statistics#

Contributors List

New Contributors

Good first issue#

Issue #5451#

Link: https://github.com/apache/apisix/issues/5451

Issue description:

Nginx comes with a response content replacement library that can replace partial content: http://nginx.org/en/docs/http/ngx_http_sub_module.html

sub_filter '<a href="http://127.0.0.1:8080/'  '<a href="https://$host/';

There is a library that supports regular substitution (as I remember Openresty already supports it by default): ngx_http_substitutions_filter_module, which can replace content with regular expressions: ngx_http_substitutions_filter_module

subs_filter_types text/html text/css text/xml;subs_filter st(\d*).example.com $1.example.com ir;subs_filter a.example.com s.example.com;subs_filter http://$host https://$host;

However, it seems that APISIX's response-rewrite plugin only supports full replacement, which is equivalent to directly replacing all responses with the return set by the plugin, and does not support partial content replacement:

curl http://127.0.0.1:9080/apisix/admin/routes/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{    "methods": ["GET"],    "uri": "/test/index.html",    "plugins": {        "response-rewrite": {            "body": "{\"code\":\"ok\",\"message\":\"new json body\"}",            "headers": {                "X-Server-id": 3,                "X-Server-status": "on",                "X-Server-balancer_addr": "$balancer_ip:$balancer_port"            },            "vars":[                [ "status","==","200" ]            ]        }    },    "upstream": {        "type": "roundrobin",        "nodes": {            "127.0.0.1:80": 1        }    }}'

Does this plugin support partial replacement or regular replacement? If not, is there any other solution for APISIX?

Issue #5647#

Link: https://github.com/apache/apisix/issues/5647

Issue description:

The current documentation provides a way to install APISIX directly using RPM on CentOS7, but the current APISIX has switched its dependency to apisix-base version without providing its RPM installation method, which will cause the installation to fail.

Issue Screenshot

Is it possible to add the command for installing the RPM for apisix-base.

Highlights of Recent Features#

The Apache APISIX project website and the Github issue have accumulated a wealth of documentation and experience, so if you encounter problems, you can read the documentation, search the issue with keywords, or participate in the discussion on the issue to put forward your own ideas and practical experience.

Recent Blog Recommendations#