htaccess to disable wordpress search domain / ? s = testwordpress .htaccess file hacked.htaccess password...

Proof by Induction - New to proofs

Why is my solution for the partial pressures of two different gases incorrect?

What's a good word to describe a public place that looks like it wouldn't be rough?

What's the rationale behind the objections to these measures against human trafficking?

On what did Lego base the appearance of the new Hogwarts minifigs?

How Should I Define/Declare String Constants

Why is working on the same position for more than 15 years not a red flag?

Meaning of すきっとした

Finding the number of integers that are a square and a cube at the same time

What can I substitute for soda pop in a sweet pork recipe?

Can I become debt free or should I file for bankruptcy? How do I manage my debt and finances?

What prevents the construction of a CPU with all necessary memory represented in registers?

What are these green text/line displays shown during the livestream of Crew Dragon's approach to dock with the ISS?

How can I mix up weapons for large groups of similar monsters/characters?

Is divide-by-zero a security vulnerability?

How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?

Why is this code uniquely decodable?

What do the pedals on grand pianos do?

Sometimes a banana is just a banana

The change directory (cd) command is not working with a USB drive

Where was Karl Mordo in Infinity War?

Why is commutativity optional in multiplication for rings?

ip vs ifconfig commands pros and cons

Which aircraft had such a luxurious-looking navigator's station?



htaccess to disable wordpress search domain / ? s = test


wordpress .htaccess file hacked.htaccess password protection not working in localhostHtaccess regex working strangeRedirecting a query search from old domain to the new domain using .htaccesshtaccess redirect of search resultsFailure htaccess regaxHow to disable the automatic redirection in WordPress-htaccess-fileApache .htaccess: do not redirect ifWordPress .htaccess mod_expiresWhat does this wordpress .htaccess rule do?













1















my wordpress blog get's bombarded with senseless search requests.



htaccess to disable wordpress search domain / ? s = test



senseless wordpress search requests



the search request is in Korean?



wordpress_senseless_searches_result



which translates as:



wordpress_senseless_searches_result_translated



so either its DDoS or SPAM.



the IPs in question are:



host 66.249.64.24
24.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-24.googlebot.com.



host 66.249.64.26
26.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-26.googlebot.com.



something is wrong with iptables and i can not block the requests via IP.



the requests look like this:



domain.com/?s=StrangeKoreanSearchPattern


what regex would i need in .htaccess to make all searchs password protected?



# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

<FilesMatch "wp-login.php">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>

# DOES NOT WORK :-|
<FilesMatch "index.php?s=.*">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>


thanks!










share|improve this question


















  • 1





    Do you need to block all requests that contain the query string s=<something> or just s=<Korean-something> (or non-English language)? Are you wanting to block these requests for all users, or trigger a password dialog (as in your example)?

    – MrWhite
    7 hours ago
















1















my wordpress blog get's bombarded with senseless search requests.



htaccess to disable wordpress search domain / ? s = test



senseless wordpress search requests



the search request is in Korean?



wordpress_senseless_searches_result



which translates as:



wordpress_senseless_searches_result_translated



so either its DDoS or SPAM.



the IPs in question are:



host 66.249.64.24
24.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-24.googlebot.com.



host 66.249.64.26
26.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-26.googlebot.com.



something is wrong with iptables and i can not block the requests via IP.



the requests look like this:



domain.com/?s=StrangeKoreanSearchPattern


what regex would i need in .htaccess to make all searchs password protected?



# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

<FilesMatch "wp-login.php">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>

# DOES NOT WORK :-|
<FilesMatch "index.php?s=.*">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>


thanks!










share|improve this question


















  • 1





    Do you need to block all requests that contain the query string s=<something> or just s=<Korean-something> (or non-English language)? Are you wanting to block these requests for all users, or trigger a password dialog (as in your example)?

    – MrWhite
    7 hours ago














1












1








1








my wordpress blog get's bombarded with senseless search requests.



htaccess to disable wordpress search domain / ? s = test



senseless wordpress search requests



the search request is in Korean?



wordpress_senseless_searches_result



which translates as:



wordpress_senseless_searches_result_translated



so either its DDoS or SPAM.



the IPs in question are:



host 66.249.64.24
24.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-24.googlebot.com.



host 66.249.64.26
26.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-26.googlebot.com.



something is wrong with iptables and i can not block the requests via IP.



the requests look like this:



domain.com/?s=StrangeKoreanSearchPattern


what regex would i need in .htaccess to make all searchs password protected?



# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

<FilesMatch "wp-login.php">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>

# DOES NOT WORK :-|
<FilesMatch "index.php?s=.*">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>


thanks!










share|improve this question














my wordpress blog get's bombarded with senseless search requests.



htaccess to disable wordpress search domain / ? s = test



senseless wordpress search requests



the search request is in Korean?



wordpress_senseless_searches_result



which translates as:



wordpress_senseless_searches_result_translated



so either its DDoS or SPAM.



the IPs in question are:



host 66.249.64.24
24.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-24.googlebot.com.



host 66.249.64.26
26.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-26.googlebot.com.



something is wrong with iptables and i can not block the requests via IP.



the requests look like this:



domain.com/?s=StrangeKoreanSearchPattern


what regex would i need in .htaccess to make all searchs password protected?



# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

<FilesMatch "wp-login.php">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>

# DOES NOT WORK :-|
<FilesMatch "index.php?s=.*">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</FilesMatch>


thanks!







linux .htaccess apache2 regex






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 10 hours ago









canoodlecanoodle

283




283








  • 1





    Do you need to block all requests that contain the query string s=<something> or just s=<Korean-something> (or non-English language)? Are you wanting to block these requests for all users, or trigger a password dialog (as in your example)?

    – MrWhite
    7 hours ago














  • 1





    Do you need to block all requests that contain the query string s=<something> or just s=<Korean-something> (or non-English language)? Are you wanting to block these requests for all users, or trigger a password dialog (as in your example)?

    – MrWhite
    7 hours ago








1




1





Do you need to block all requests that contain the query string s=<something> or just s=<Korean-something> (or non-English language)? Are you wanting to block these requests for all users, or trigger a password dialog (as in your example)?

– MrWhite
7 hours ago





Do you need to block all requests that contain the query string s=<something> or just s=<Korean-something> (or non-English language)? Are you wanting to block these requests for all users, or trigger a password dialog (as in your example)?

– MrWhite
7 hours ago










2 Answers
2






active

oldest

votes


















1














After a litte bit of research and testing I would say following htaccess entry should work:



<If "%{QUERY_STRING} =~ /.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>


Source: https://stackoverflow.com/questions/31903448/htaccess-deny-specific-get-parameter



To clarify what this is doing:
If the Query String (the string that begins with "?" after "domain.com/") contains "?s=", then require a valid user from the .htpasswd file.






share|improve this answer










New contributor




r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    realized there is another way to trigger wordpress search: domain.com/?search=bla should be covered by another <If statement with: <If "%{QUERY_STRING} =~ /.?search=/"> thanks! apache is holding the world record on complicated software httpd.apache.org/docs/2.4/expr.html

    – canoodle
    8 hours ago













  • argh: the regex also triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl

    – canoodle
    8 hours ago











  • What is the reason for the .? part in your regex? (It's not doing anything.)

    – MrWhite
    7 hours ago











  • The dot was my fault. It should have been a backslash. The backslash would escape the question mark and the regex result would excactly be ?s= .

    – r00tusr
    1 hour ago











  • @canoodle i have no idea why it triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl. Does this url contain s= anywhere?

    – r00tusr
    58 mins ago



















1














thanks for your answer, .htaccess and regex are two beasts in one.



modified your answer and it seems to work fine now. #Thanks!



<If "%{QUERY_STRING} =~ /^.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>

<If "%{QUERY_STRING} =~ /^.?search=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>





share|improve this answer
























  • No need for two blocks (and that .? bit would seem to be superfluous?)... it's a regex, so you can combine the two. For example: /^(s|search)=/

    – MrWhite
    7 hours ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f956570%2fhtaccess-to-disable-wordpress-search-domain-s-test%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














After a litte bit of research and testing I would say following htaccess entry should work:



<If "%{QUERY_STRING} =~ /.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>


Source: https://stackoverflow.com/questions/31903448/htaccess-deny-specific-get-parameter



To clarify what this is doing:
If the Query String (the string that begins with "?" after "domain.com/") contains "?s=", then require a valid user from the .htpasswd file.






share|improve this answer










New contributor




r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    realized there is another way to trigger wordpress search: domain.com/?search=bla should be covered by another <If statement with: <If "%{QUERY_STRING} =~ /.?search=/"> thanks! apache is holding the world record on complicated software httpd.apache.org/docs/2.4/expr.html

    – canoodle
    8 hours ago













  • argh: the regex also triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl

    – canoodle
    8 hours ago











  • What is the reason for the .? part in your regex? (It's not doing anything.)

    – MrWhite
    7 hours ago











  • The dot was my fault. It should have been a backslash. The backslash would escape the question mark and the regex result would excactly be ?s= .

    – r00tusr
    1 hour ago











  • @canoodle i have no idea why it triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl. Does this url contain s= anywhere?

    – r00tusr
    58 mins ago
















1














After a litte bit of research and testing I would say following htaccess entry should work:



<If "%{QUERY_STRING} =~ /.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>


Source: https://stackoverflow.com/questions/31903448/htaccess-deny-specific-get-parameter



To clarify what this is doing:
If the Query String (the string that begins with "?" after "domain.com/") contains "?s=", then require a valid user from the .htpasswd file.






share|improve this answer










New contributor




r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    realized there is another way to trigger wordpress search: domain.com/?search=bla should be covered by another <If statement with: <If "%{QUERY_STRING} =~ /.?search=/"> thanks! apache is holding the world record on complicated software httpd.apache.org/docs/2.4/expr.html

    – canoodle
    8 hours ago













  • argh: the regex also triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl

    – canoodle
    8 hours ago











  • What is the reason for the .? part in your regex? (It's not doing anything.)

    – MrWhite
    7 hours ago











  • The dot was my fault. It should have been a backslash. The backslash would escape the question mark and the regex result would excactly be ?s= .

    – r00tusr
    1 hour ago











  • @canoodle i have no idea why it triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl. Does this url contain s= anywhere?

    – r00tusr
    58 mins ago














1












1








1







After a litte bit of research and testing I would say following htaccess entry should work:



<If "%{QUERY_STRING} =~ /.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>


Source: https://stackoverflow.com/questions/31903448/htaccess-deny-specific-get-parameter



To clarify what this is doing:
If the Query String (the string that begins with "?" after "domain.com/") contains "?s=", then require a valid user from the .htpasswd file.






share|improve this answer










New contributor




r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










After a litte bit of research and testing I would say following htaccess entry should work:



<If "%{QUERY_STRING} =~ /.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>


Source: https://stackoverflow.com/questions/31903448/htaccess-deny-specific-get-parameter



To clarify what this is doing:
If the Query String (the string that begins with "?" after "domain.com/") contains "?s=", then require a valid user from the .htpasswd file.







share|improve this answer










New contributor




r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this answer



share|improve this answer








edited 8 hours ago





















New contributor




r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









answered 9 hours ago









r00tusrr00tusr

263




263




New contributor




r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






r00tusr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    realized there is another way to trigger wordpress search: domain.com/?search=bla should be covered by another <If statement with: <If "%{QUERY_STRING} =~ /.?search=/"> thanks! apache is holding the world record on complicated software httpd.apache.org/docs/2.4/expr.html

    – canoodle
    8 hours ago













  • argh: the regex also triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl

    – canoodle
    8 hours ago











  • What is the reason for the .? part in your regex? (It's not doing anything.)

    – MrWhite
    7 hours ago











  • The dot was my fault. It should have been a backslash. The backslash would escape the question mark and the regex result would excactly be ?s= .

    – r00tusr
    1 hour ago











  • @canoodle i have no idea why it triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl. Does this url contain s= anywhere?

    – r00tusr
    58 mins ago














  • 1





    realized there is another way to trigger wordpress search: domain.com/?search=bla should be covered by another <If statement with: <If "%{QUERY_STRING} =~ /.?search=/"> thanks! apache is holding the world record on complicated software httpd.apache.org/docs/2.4/expr.html

    – canoodle
    8 hours ago













  • argh: the regex also triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl

    – canoodle
    8 hours ago











  • What is the reason for the .? part in your regex? (It's not doing anything.)

    – MrWhite
    7 hours ago











  • The dot was my fault. It should have been a backslash. The backslash would escape the question mark and the regex result would excactly be ?s= .

    – r00tusr
    1 hour ago











  • @canoodle i have no idea why it triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl. Does this url contain s= anywhere?

    – r00tusr
    58 mins ago








1




1





realized there is another way to trigger wordpress search: domain.com/?search=bla should be covered by another <If statement with: <If "%{QUERY_STRING} =~ /.?search=/"> thanks! apache is holding the world record on complicated software httpd.apache.org/docs/2.4/expr.html

– canoodle
8 hours ago







realized there is another way to trigger wordpress search: domain.com/?search=bla should be covered by another <If statement with: <If "%{QUERY_STRING} =~ /.?search=/"> thanks! apache is holding the world record on complicated software httpd.apache.org/docs/2.4/expr.html

– canoodle
8 hours ago















argh: the regex also triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl

– canoodle
8 hours ago





argh: the regex also triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl

– canoodle
8 hours ago













What is the reason for the .? part in your regex? (It's not doing anything.)

– MrWhite
7 hours ago





What is the reason for the .? part in your regex? (It's not doing anything.)

– MrWhite
7 hours ago













The dot was my fault. It should have been a backslash. The backslash would escape the question mark and the regex result would excactly be ?s= .

– r00tusr
1 hour ago





The dot was my fault. It should have been a backslash. The backslash would escape the question mark and the regex result would excactly be ?s= .

– r00tusr
1 hour ago













@canoodle i have no idea why it triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl. Does this url contain s= anywhere?

– r00tusr
58 mins ago





@canoodle i have no idea why it triggers on domain.com/wp-json/shariff/v1/share_counts?url=coolArticleUrl. Does this url contain s= anywhere?

– r00tusr
58 mins ago













1














thanks for your answer, .htaccess and regex are two beasts in one.



modified your answer and it seems to work fine now. #Thanks!



<If "%{QUERY_STRING} =~ /^.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>

<If "%{QUERY_STRING} =~ /^.?search=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>





share|improve this answer
























  • No need for two blocks (and that .? bit would seem to be superfluous?)... it's a regex, so you can combine the two. For example: /^(s|search)=/

    – MrWhite
    7 hours ago
















1














thanks for your answer, .htaccess and regex are two beasts in one.



modified your answer and it seems to work fine now. #Thanks!



<If "%{QUERY_STRING} =~ /^.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>

<If "%{QUERY_STRING} =~ /^.?search=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>





share|improve this answer
























  • No need for two blocks (and that .? bit would seem to be superfluous?)... it's a regex, so you can combine the two. For example: /^(s|search)=/

    – MrWhite
    7 hours ago














1












1








1







thanks for your answer, .htaccess and regex are two beasts in one.



modified your answer and it seems to work fine now. #Thanks!



<If "%{QUERY_STRING} =~ /^.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>

<If "%{QUERY_STRING} =~ /^.?search=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>





share|improve this answer













thanks for your answer, .htaccess and regex are two beasts in one.



modified your answer and it seems to work fine now. #Thanks!



<If "%{QUERY_STRING} =~ /^.?s=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>

<If "%{QUERY_STRING} =~ /^.?search=/">
AuthName "WordPress Admin"
AuthType Basic
AuthUserFile /home/admin/web/.htpasswd
require valid-user
</If>






share|improve this answer












share|improve this answer



share|improve this answer










answered 7 hours ago









canoodlecanoodle

283




283













  • No need for two blocks (and that .? bit would seem to be superfluous?)... it's a regex, so you can combine the two. For example: /^(s|search)=/

    – MrWhite
    7 hours ago



















  • No need for two blocks (and that .? bit would seem to be superfluous?)... it's a regex, so you can combine the two. For example: /^(s|search)=/

    – MrWhite
    7 hours ago

















No need for two blocks (and that .? bit would seem to be superfluous?)... it's a regex, so you can combine the two. For example: /^(s|search)=/

– MrWhite
7 hours ago





No need for two blocks (and that .? bit would seem to be superfluous?)... it's a regex, so you can combine the two. For example: /^(s|search)=/

– MrWhite
7 hours ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Server Fault!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f956570%2fhtaccess-to-disable-wordpress-search-domain-s-test%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

117736 Шеррод Примітки | Див. також | Посилання | Навігаційне...

As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

Маріан Котлеба Зміст Життєпис | Політичні погляди |...