The Wayback Machine - https://web.archive.org/web/20220321151110/https://github.com/digitalocean/nginxconfig.io/issues/316
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wordpress.conf disable xmlrpc service by default #316

Open
RebelliousWhiz opened this issue Dec 29, 2021 · 2 comments
Open

wordpress.conf disable xmlrpc service by default #316

RebelliousWhiz opened this issue Dec 29, 2021 · 2 comments

Comments

@RebelliousWhiz
Copy link

@RebelliousWhiz RebelliousWhiz commented Dec 29, 2021

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?

@MattIPv4
Copy link
Member

@MattIPv4 MattIPv4 commented Dec 29, 2021

Hey! I think either would be a good solution here -- there should be patterns in the source already for showing warnings to a user, or a secondary toggle option would also be a good way to solve this.

@RebelliousWhiz
Copy link
Author

@RebelliousWhiz RebelliousWhiz commented Dec 29, 2021

Hi Matt! Considering most people using nginxconfig.io are noobs (I am a 100% noob also), I'd say it's better to have a secondary toggle option and add some comments.

For example:

[ ] Allow xmlrpc access

  • xmlrpc allows you to control WordPress sites by using WordPress applications or other plugins (like Jetpack) if you use them.

Regards,
Andy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment