These interfere with JSON-LD activitypub requests because
apparently the '; profile="..."' part is matched by that humongous
rule 920600 regexp and ModSecurity thinks it's a charset.

Apparently gotosocial uses it for profile discovery.

The cache/.htaccess mechanism should actually be moved into
the apache2 config, instead of the current hackish solution...

Needed to find wp-cli, a dependency of noblogs-cli.

The WP-Supercache Apache caching will anyway cover NGINX
requests for 300s.

In case it's a tmpfs.

Using what is hopefully the right format for the tx.allowed_request_content_type
configuration variable.

Only comment changes, illustrating the new defaults.

This reverts commit 9c69d4de.

This reverts commit 4acd8455.

And disallow all requests that are not static content.

Fixes issue ai/noblogs-wp#89.

These should help with converting widgets from legacy to
new 'blocks'.