[wp-trac] [WordPress Trac] #18852: Nginx rewrite rules

WordPress Trac noreply at wordpress.org
Fri Jul 5 22:37:08 UTC 2013

#18852: Nginx rewrite rules
 Reporter:  johnbillion              |       Owner:  johnbillion
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  Future Release
Component:  Rewrite Rules            |     Version:  3.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |
Changes (by mbijon):

 * cc: mike@… (added)


 I think the importance of this has escalted since this ticket was opened
 in 2011.

 Since Jeremy Felt made nginx easy & standard in VVV,
 https://github.com/10up/varying-vagrant-vagrants, I've been talking to
 more people about it & almost every major WP dev shop is running nginx.
 Most of us have our own configs & a patchwork of things we do to support
 it, so it might be time to put more engineering into making it more

 Worth noting that on Top 1,000 sites, nginx has surpassed Apache in



 Is it worth extending this ticket, or adding a separate one for
 WP_Rewrite's non_wp_rules()?
 * http://codex.wordpress.org/Function_Reference/WP_Rewrite#Non-

 If we're displaying nginx rules in the UX, then that method should alert
 in some way too. Or, better, get refactored to write nginx rules too.

 What if we implemented something like the $scheme parameter that handles
 HTTP/HTTPS URLs now? That would enable plugins to add more-extensive nginx
 rule support, without the need to debug & maintain this in core (yet).
 (Plus, plugins have a faster|easier update cycle in the event new rules
 are needed to fix security issues)

Ticket URL: <http://core.trac.wordpress.org/ticket/18852#comment:25>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list