NT versions

[wilderness]

Could somebody provide if the double-parenthese near the end is correct?

(NT\ (4\.0|5\.(01?|1|2)|6\.(01?|1|2))|

Believe it closes the opening "(NT"

[incrediBILL]

Looks to me like you need one more ')' somewhere as I think it just closes the '(4' as shown.

[wilderness]

Many thanks Bill.

I'm actually attempting to add more versions of "6" here.
Initially I tried simply copying the versions from "5", however that failed and resulted in a server 500.

I've no clue if six has/had anything higher than ".1"?

No clue what the forum software is going to do to the spaces!

The old line looked like this in instance:
NT\ (4\.0|5\.(01?|1|2)|6\.01?)(\)|;\ [^)])

In another instance:
NT\ (5\.(01?|1|2)|6\.0)(;\ .|\))

and yet another
(NT\ (4\.0|5\.(01?|1|2)|6\.0)|98;\ Win\ 9x\ 4\.90|98|95)

[lucy24]

Whoops! Forgot to refresh the tab before putting in my own 2¢.
____

(NT\ (4\.0|5\.(01?|1|2)|6\.(01?|1|2))|

You've got one more opening than closing parenthesis-- and that's what you ought to have, since the structure is

(blahblah|

presumably followed by further

blahblah)

that you've left out.

x1 = (01?|1|2)
x2 = (01?|1|2)
y = (4\.0|5\.{x1}|6\.{x2})
z = (NT\ {y}|

As it were.

Why can't it just say

(NT\ (4\.0|[56]\.(01?|1|2))|
?

[wilderness]

lucy,
Each of those three lines do different things and are part of more extensive filtering.

They were in place for lots of years and functioned fine.

At this point, I've temporarily removed these old browser sections. However, I'd still like to use them later and update the 6+ versions.

Why can't it just say
(NT\ (4\.0|[56]\.(01?|1|2))|

I'll try this.
Many thanks.

I've become involved with websites again, and my entire mod_rewrite section is not functioning (yes mod_rewrite is active on the server.

I've had to add error documents (which I'd never used previously), as well as "Files" container for a php contact form.
The error documents functioned for a short while (despite the non-working mod_write) last night and one denied visitor (mod_access) returned properly (this correct function was the result of locating two missing begins-with-anchors):

HTTP/1.1" 301 248
HTTP/1.1" 403 533
/custom403.html

Additionally, in order to accomplish the above, I removed the LIMIT container and made it a FILE container, which resulted in a log format that I didn't care for. Once removing the FILE container (restoring LIMIT) I had to wait for the daily server reboot to restore logs in the previous format.

Unfortunately, my htaccess is quite large.

I.m attempting to go through it section by section and have even split an approximate 900 lines of IP's from two former sections to four sections.

Also getting some loops.

[lucy24]

my entire mod_rewrite section is not functioning (yes mod_rewrite is active on the server

Of course you remembered to say RewriteEngine On in each separate htaccess that uses mod_rewrite ;) You might try "on" (lower case) on the remote chance you've got a snarky server. Apache's docs actually have it that way.

The idea of a server without mod_rewrite is enough to make one's blood run cold.

have even split an approximate 900 lines of IP's from two former sections to four sections

Ugh. Mine's around 200 lines-- counting AWS and China-- and I think that's too fat!

Also getting some loops.

You mean the kind where error logs say "This is going to redirect forever" and slap on a 403 after ten iterations? Make sure there's nothing preventing your unwanted visitors from seeing the error pages. That counts as an infinite redirect: ask for file, get refused, ask (internally) for custom 403 document, get refused (because it's just another request), ask (internally) for custom 403 document, get refused... and so on. You may remember I wrestled with that one pretty recently.

[wilderness]

"on' was lower case and I thought that might be am issue and changed it to "On" and no effect.

Jim's error document explanation (which I located recently in the Apache forum and for that "deny, allow" conversation) provided the "FILES" container being used (rather than Limit), and it did function for me in the files container (briefly). Unfortunately I couldn't tolerate the log format (somebody in this forum submits server names rather than IP's; perhaps dstiles).

I'm just changing some much at that same time and that is certainly not the way to deal with htaccess and/or regex.

FWIW, for more than a decade I used "allow,deny" and finally made the change to "deny,allow".

[dstiles]

Not me! I usually submit IPs since that's how my (non-htaccess) blocking system works. :)

[lucy24]

You mean pfui? The ones that look like this?

out-sw248.tfbnw.net

For several days last August my server went wonky and everything came through in that form. Except, ahem, some robots that utterly failed the rDNS test, I guess. It was horrible while it lasted.

[wilderness]

You mean pfui? The ones that look like this?

That's it, Annie's the critter ;)

Saw a note in the Apache forum that her server crashed.
Hope she's getting closer.