Here’s the relevant extract from the article:
Pretty permalinks are available under:
- Apache web server with the mod_rewrite module
- Nginx using try-files, e.g. according to this tutorial
- Hiawatha web server with UrlToolkit support enabled.
- Lighttpd using a 404 handler or mod_rewrite
- Caddy using rewrite, e.g. according to this tutorial
Clicking the link to the tutorial takes me to a Caddy V1 article.
I’d like to propose the following changes to the WordPress documentation team:
- Revise this extract to read as follows:
Pretty permalinks are available under:
- Apache web server with the mod_rewrite module
- Nginx using try-files, e.g. according to this tutorial
- Hiawatha web server with UrlToolkit support enabled.
- Lighttpd using a 404 handler or mod_rewrite
- Caddy automatically in a default WordPress installation.
This is based on feedback from @francislavoie in this post Process check: Spreading the Caddy Word - #16 by francislavoie
- Just further down in the WP article, in the section Using “Pretty” permalinks, I propose adding the following bullet point:
- For Caddy, a web server that supports HTTPS natively, the rewrite rule may need to be adjusted if WordPress files are moved to a subdirectory. Refer to Using Caddy to give WordPress its own directory for details.
This is based on feedback from @Whitestrake in this post Process check: Spreading the Caddy Word - #19 by Whitestrake
Before I submit a request to update the article, I just want to make sure that I’ve interpreted the feedback correctly and this is reflected in the proposed text amendments. Suggestions for improving the proposed text are also welcome.