Postings by James Moe

Blocking particular URL/file patterns

apache 2.4.39
linux 4.12.14-lp151.28.7-default x86_64

Our site has beset with numerous search engine queries for URLs that
have *never* existed on the site. They have the form:


where the digits are randomly changed. The search bots of Google and
Bing are the most prevalent producing 1000s of 404s per day. Not a
particular CPU burden, to be sure.

Question about order of execution

apache 2.4.38
linux 2.26.32 x86_64

We have de-commissioned a domain,, and have added
Redirects to point to the new locations for its information.
We recently received a query that a visitor's browser was complaining
about how unsafe was, what with an expired SSL
certificate and all. I am unclear how they got to the old site at all.

My question is: Does the certificate validation occur before or after
processing <.htaccess>?

----[ .htaccess ]----
Options +ExecCGI
# 20180722 jmm: De-commissioned.

bounced messages

I received a note from the list manager complaining that our server
has rejected an unconscionable number of message.
Has there been some configuration change of the mailing list recently?

There are reasons for the rejections: our SPAM filter.
1. The filter found one set of messages being sent from a blocklisted
site (, and rejected the messages.
2. The filter uses a greylist to decide about the validity if a sender
(nearly 2/3 of spam is rejected this way).

"Permissions" lost after upgrade to 2.4.33

opensuse LEAP 15
linux 4.12.14-lp150.11-default x86_64
apache2 2.4.33

After the upgrade from v2.4.23 to v2.4.33, https requests yield error
Access forbidden!
You don't have permission to access the requested directory. There is
either no index document or the directory is read-protected.

Neither of the stated reasons are true.

Apache2 does not start after OS upgrade

opensuse LEAP 15
linux 4.12.14-lp150.11-default x86_64
apache2 2.4.33

On opensuse v42.3 apache2 v2.4.23 worked fine. On opensuse 15.0 apache2
v2.4.33 refuses to start.

Below is all of the info I could find regarding its failure to start.
The bit about "unit configuration" seems helpful, if only I knew what it

The part about "<whatever>_module is already loaded, skipping" was
listed in LEAP 42.3 as well.