Copilot commented on code in PR #1995:
URL: https://github.com/apache/apisix-website/pull/1995#discussion_r2867263322


##########
blog/en/blog/2026/02/28/2026-feb-monthly-report.md:
##########
@@ -0,0 +1,141 @@
+---
+title: "2026 Monthly Report (February 01 - February 28)"
+keywords: ["Apache APISIX", "API Gateway", "Monthly Report", "Contributor"]
+description: Our monthly Apache APISIX community report generates insights 
into the project's monthly developments. The reports provide a pathway into the 
Apache APISIX community, ensuring that you stay well-informed and actively 
involved.
+tags: [Community]
+image: 
https://static.api7.ai/uploads/2026/02/28/wFO4NRZJ_2026-feb-monthly-report-cover-en.webp
+---
+
+> Recently, we've introduced and updated some new features, including support 
for retrieving stream health check data via the Control API, and support for 
configuring the header prefix in `limit-count` plugin rules, etc. For more 
details, please read this month's newsletter.
+
+<!--truncate-->
+
+## Introduction
+
+From its inception, the Apache APISIX project has embraced the ethos of 
open-source community collaboration, propelling it into the ranks of the most 
active global open-source API gateway projects. The proverbial wisdom of 
'teamwork makes the dream work' rings true in our way and is made possible by 
the collective effort of our community.
+
+From February 1st to February 28th, 11 contributors made 45 commits to Apache 
APISIX. We sincerely appreciate your contributions to Apache APISIX.
+
+## Contributor Statistics
+
+![Apache APISIX Contributors 
List](https://static.api7.ai/uploads/2026/02/28/iQbt1dLQ_2026-feb-contributor-list.webp)
+
+![New Contributors 
List](https://static.api7.ai/uploads/2026/02/28/aetNLUjx_2026-feb-new-contributors.webp)
+
+## Good First Issue
+
+### Issue #13043
+
+**Link**: https://github.com/apache/apisix/issues/13043
+
+**Description**: Fix incorrect parameter names in the Chinese documentation 
for the `limit-count`, `limit-req`, and `limit-conn` plugins.
+
+## Feature Highlights
+
+### 1. Make CLS Scheme Configurable and Default to `https`
+
+PR: https://github.com/apache/apisix/pull/13009
+
+Contributor: [shreemaan-abhishek](https://github.com/shreemaan-abhishek)
+
+This PR makes the scheme for accessing CLS (Cloud Log Service) configurable, 
addressing the security risk of using `http` by default. The default scheme is 
now set to `https` to enhance data transmission security.
+
+### 2. Throw Panic Error When Parent Node Is Invalid in `limit-count` Plugin
+
+PR: https://github.com/apache/apisix/pull/13030
+
+Contributor: [janiussyafiq](https://github.com/janiussyafiq)
+
+This PR refactors the `limit-count` plugin to throw a panic error when an 
invalid parent is detected, preventing error states from propagating.
+
+### 3. Support Stream Health Check Data Retrieval via Control API
+
+PR: https://github.com/apache/apisix/pull/12996
+
+Contributor: [shreemaan-abhishek](https://github.com/shreemaan-abhishek)
+
+This PR fixes the issue where upstream health check status in stream mode 
could not be obtained via the Control API. Previously, the `/v1/healthcheck` 
endpoint only returned health check status for HTTP upstreams, leaving stream 
route health checks invisible. The endpoint now also returns health check 
information for stream upstreams, ensuring complete visibility.
+
+### 4. Support Configuring Header Prefix in `limit-count` Plugin Rules
+
+PR: https://github.com/apache/apisix/pull/13004
+
+Contributor: [shreemaan-abhishek](https://github.com/shreemaan-abhishek)
+
+This PR adds the ability to configure a `header` prefix in the `limit-count` 
plugin to differentiate rate-limiting response headers when multiple rules are 
triggered simultaneously. Users can customize the prefix via `header_prefix` 
(defaults to the index of the currently executed rule), allowing isolation of 
response headers across multiple rate-limiting rules and avoiding status 
information confusion.

Review Comment:
   Feature highlight #4 says you can configure a `header` prefix, but the 
option mentioned is `header_prefix`. This reads like `header` is the actual 
field name; please adjust the text to consistently reference `header_prefix` 
(or remove backticks around “header”) to avoid misconfiguring the plugin.
   ```suggestion
   This PR adds the ability to configure a `header_prefix` prefix in the 
`limit-count` plugin to differentiate rate-limiting response headers when 
multiple rules are triggered simultaneously. Users can customize the prefix via 
`header_prefix` (defaults to the index of the currently executed rule), 
allowing isolation of response headers across multiple rate-limiting rules and 
avoiding status information confusion.
   ```



##########
blog/zh/blog/2026/02/28/2026-feb-monthly-report.md:
##########
@@ -0,0 +1,141 @@
+---
+title: "2026 社区月报 (02.01 - 02.28)"
+keywords: ["Apache APISIX", "API 网关", "社区月报", "贡献者"]
+description: Apache APISIX 社区的月报旨在帮助社区成员更全面地了解社区的最新动态,方便大家参与到 Apache APISIX 
社区中来。
+tags: [Community]
+image: 
https://static.api7.ai/uploads/2026/02/28/EDuu5wUR_2026-feb-monthly-report-cover-cn.webp
+---
+
+> 最近,我们引入并更新了一些功能,包括为支持通过 Control API 获取 Stream 健康检查数据、`elasticsearch-logger` 
插件支持通过请求头进行认证、在 `limit-conn` 和 `ai-rate-limiting` 插件中支持 `rules` 
配置等。有关更多细节,请阅读本期月报。
+
+<!--truncate-->
+
+## 导语
+
+Apache APISIX 项目始终秉承着开源社区协作的精神,自问世起便崭露头角,如今已经成为全球最活跃的开源 API 
网关项目之一。正如谚语所言,“众人拾柴火焰高”,这一辉煌成就,得益于整个社区伙伴的协同努力。
+
+从 2026.02.01 至 2026.02.28,有 11 名开发者提交了 45 个 commits,为 Apache APISIX 
做出了重要贡献。感谢这些伙伴们对 Apache APISIX 的无私支持!正是因为你们的付出,才能让 Apache APISIX 项目不断改进、提升和壮大。
+
+## 贡献者统计
+
+![贡献者名单](https://static.api7.ai/uploads/2026/02/28/iQbt1dLQ_2026-feb-contributor-list.webp)
+
+![新晋贡献者](https://static.api7.ai/uploads/2026/02/28/aetNLUjx_2026-feb-new-contributors.webp)
+
+## Good First Issue
+
+### Issue #13043
+
+**链接**:https://github.com/apache/apisix/issues/13043
+
+**问题描述**:修复 `limit-count`、`limit-req` 和 `limit-conn` 插件中文文档中的参数名称错误。
+
+## 近期亮点功能
+
+### 1. 将云日志服务的 scheme 配置化,默认设置为 `https`
+
+相关 PR:https://github.com/apache/apisix/pull/13009
+
+贡献者:[shreemaan-abhishek](https://github.com/shreemaan-abhishek)
+
+本 PR 将访问 CLS(云日志服务)的 scheme 改为可配置项,解决此前默认使用 `http` 的安全隐患,并将默认 scheme 调整为 
`https` 以提升数据传输安全性。
+
+### 2. 在 `limit-count` 插件中,当父节点无效时抛出 panic 错误
+
+相关 PR:https://github.com/apache/apisix/pull/13030
+
+贡献者:[janiussyafiq](https://github.com/janiussyafiq)
+
+本 PR 对 `limit-count` 插件进行重构,当检测到无效的父节点时直接抛出 panic 错误,避免错误状态继续传播。
+
+### 3. 支持通过 Control API 获取 Stream 健康检查数据
+
+相关 PR:https://github.com/apache/apisix/pull/12996
+
+贡献者:[shreemaan-abhishek](https://github.com/shreemaan-abhishek)
+
+本 PR 修复了 Stream 模式下的上游健康检查状态无法通过 Control API 获取的问题。此前 `/v1/healthcheck` 接口仅返回 
HTTP 上游的健康检查状态,导致 Stream 路由的健康检查数据无法显示。现在该接口已扩展支持返回 Stream 
上游的健康检查信息,确保所有健康检查状态都能被完整展示。
+
+### 4. 在 `limit-count` 插件的规则中支持配置 `header` 前缀
+
+相关 PR:https://github.com/apache/apisix/pull/13004
+
+贡献者:[shreemaan-abhishek](https://github.com/shreemaan-abhishek)
+
+本 PR 为 `limit-count` 插件新增 `header` 前缀配置能力,用于在多条规则同时触发时区分不同限流状态的响应头。用户可通过配置 
`header_prefix` 自定义前缀,默认值为当前执行规则的索引值,从而实现多条限流规则的响应头隔离,避免状态信息混淆。

Review Comment:
   Feature highlight #4 describes configuring a `header` prefix, but the actual 
configuration key referenced later is `header_prefix`. Please align the wording 
so readers don’t mistake `header` for a real config field (e.g., consistently 
refer to `header_prefix` as the option that controls the response header 
prefix).
   ```suggestion
   ### 4. 在 `limit-count` 插件的规则中支持通过 `header_prefix` 配置响应头前缀
   
   相关 PR:https://github.com/apache/apisix/pull/13004
   
   贡献者:[shreemaan-abhishek](https://github.com/shreemaan-abhishek)
   
   本 PR 为 `limit-count` 插件新增通过 `header_prefix` 
配置响应头前缀的能力,用于在多条规则同时触发时区分不同限流状态的响应头。用户可通过配置 `header_prefix` 
自定义前缀,默认值为当前执行规则的索引值,从而实现多条限流规则的响应头隔离,避免状态信息混淆。
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to