htaccess suggestions

colak · 2014-08-19 10:50:18

Nope, that also stops searches when executed within txp:(

jakob · 2014-08-19 13:34:55

Schucks. Hmm.

If you remove the ?$ so that you get RewriteCond %{QUERY_STRING} m\=any(&q\=1)? [NC] you should at least be able to conduct searches and will catch ?m=any, ?m=any&q=1 but not ?m=any&q= i.e. a search with no query string. If that also interrupts txp’s search function, I wonder if something else is at play…

colak · 2014-08-19 15:53:19

no:)
Thanks for all this Julian, It’s a real hair puller.

GugUser · 2014-08-19 16:58:12

colak wrote #283059:

(…) It’s a real hair puller.

Or hair-raising.

;-)

Last edited by GugUser (2014-08-19 17:01:44)

maniqui · 2014-08-19 23:56:10

Based on Pete’s reply, what about this?

RewriteCond %{QUERY_STRING} m=any&q=1 [OR]
RewriteCond %{QUERY_STRING} m=any&q= [OR]
RewriteCond %{QUERY_STRING} m=any [NC]
RewriteRule ^ - [F]

I’ve added the [OR] flag and removed the (unnecesary?) escaping \

Maybe this shorter version could work too:

RewriteCond %{QUERY_STRING} m=any(&q=1?)? [NC]
RewriteRule ^ - [F]

colak · 2014-08-20 05:16:12

Both of the above return the same errors as all previous ones. ie they prevent searches from within txp by generating a 403.

colak · 2014-08-21 15:28:14

Here’s a couple of solutions which semi work:)

<files /?m=any&q=|/?m=any=|/index.php?s=|/?m=any&q=1|>
order allow,deny
deny from all
</files>

and

<FilesMatch /?m=any&q=|/?m=any=|/index.php?s=|/?m=any&q=1|>
order allow,deny
deny from all
</FilesMatch>

Textpattern CMS

Textpattern CMS support forum

#13 2014-08-19 10:50:18

Re: htaccess suggestions

#14 2014-08-19 13:34:55

Re: htaccess suggestions

#15 2014-08-19 15:53:19

Re: htaccess suggestions

#16 2014-08-19 16:58:12

Re: htaccess suggestions

colak wrote #283059:

#17 2014-08-19 23:56:10

Re: htaccess suggestions

#18 2014-08-20 05:16:12

Re: htaccess suggestions

#19 2014-08-21 15:28:14

Re: htaccess suggestions

Board footer