pattern matching in RewriteCond

[roshaoar]

hello,

I currently have

RewriteCond %{REQUEST_URI} ^/wp-login.php [NC,OR]

does this also cover

/wp-login.php?action=register ?

If not, what's the syntax please?

Thanks

[g1smd]

It covers /wp-login.php?<anything-or-nothing>

%{REQUEST_URI} matches only the path part of the URL request.
It does not match protocol, hostname, port number or query string.

If you want to match a specific query string, you will need another condition testing %{QUERY_STRING}

[lucy24]

For safety's sake, make it \.php with escaped . period.

I tend to get anxious when there's a non-negative %{REQUEST_URI}. What does the body of the rule say?


g1, there's a drupal question awaiting your expert attention right next door...

[roshaoar]

Thanks!

@lucy24 - 403 -

RewriteRule (.*) - [F]

[lucy24]

So the overall rule is "If any of these conditions apply, hit them with a 403?"

I'd put the wp-login into a separate conditionless rule:

RewriteRule ^wp-login - [F]

Save the conditions for things that apply to all requests, or ones where you're saying "the request is not suchandsuch".

You can use the [NC] flag if you like. But some robots actually go away faster if they meet a 404, which is what you'd get on most servers if you ask for WP-login when the file is really called wp-login. [NC] is a smidgen more work for the server, though it's pretty far down on the list of excessive demands.

[roshaoar]

Ahh I see! Thank you, I'll make that change