Yilialinn opened a new pull request, #2143:
URL: https://github.com/apache/apisix-website/pull/2143

   Adds the supplied PHP2Shell article in English and Chinese to the 
**Vulnerabilities** category, including its two mitigation approaches, 
deployment scopes, and rollout checklist. The Chinese body and rules are 
preserved; the English article is a faithful translation, including code 
comments and figure labels.
   
   Changes:
   
   - Add matching posts dated October 24, 2026, with repository frontmatter and 
a single excerpt paragraph.
   - Include the original Chinese figures, localized English figures, and 
covers in both static asset pipelines.
   - Keep author metadata omitted, consistent with recent vulnerability posts.
   
   Validation:
   
   - Markdown lint, repository frontmatter validation, and content lint pass.
   - 35 focused checks pass, including Lua header-handling cases with mocked 
`ngx`, YAML/configuration parity, source preservation, and static asset 
availability.
   - Actual repository Astro article and card templates were rendered in an 
isolated container and inspected in Chrome at desktop and mobile widths. This 
is not a full production build.
   - All six unique reference links resolve, including both PHP announcement 
anchors.
   
   This is a **draft**. Local review identified a known Coraza Content-Type 
parsing blind spot affecting some form-field checks. The supplied content 
remains unchanged at the author's request; the finding is recorded in the local 
review report. Live APISIX/Wasm/Coraza request validation and the full 
production build/overlay/sitemap checks remain outstanding. No large local 
build was run because available disk space was below the machine's configured 
safety threshold.
   


-- 
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