digitalocean/nginxconfig.io

wordpress.conf disable xmlrpc service by default

Open

#316 建立於 2021年12月29日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)JavaScript (26,979 star) (1,978 fork)batch import
enhancementgood first issuehacktoberfesthelp wanted

描述

Sorry for not following the template. It's a straightforward question.

By enabling "WordPress-specific rules", the following codes will be added to the wordpress.conf:

# WordPress: deny general stuff
location ~* ^/(?:xmlrpc\.php|wp-links-opml\.php|wp-config\.php|wp-config-sample\.php|readme\.html|license\.txt)$ {
    deny all;
}

However, this disables xmlrpc feature, which disables WordPress mobile and desktop applications to access the site.

Should we consider adding a notice or make it optional?

貢獻者指南

技術棧
javascript
領域
devops
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
85
研究方向
Examine the existing wordpress.conf template in the project to understand where the XML RPC block rule is defined. Review the comments on the issue for any maintainer suggestions or concerns. Consider adding a checkbox in the WordPress configuration section to optionally disable XML RPC blocking, and update the template accordingly. Also, include a notice about the impact on mobile/desktop applications.