Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

security/modsecurity3-nginx: Update to 1.0.3

Changelog:

    Support http protocol versions besides 0.9, 1.0, 1.1, 2.0
    [Issue #224 - @HQuest, @martinhsv]
    Support for building with nginx configured with PCRE2
    [Issue #260 - @defanator]

Sponsored by:	Netzkommune GmbH

security/modsecurity3-nginx: Update NGINX version

PR:	261254
Sponsored by:	Netzkommune GmbH

security/modsecurity3-nginx: Update to 1.0.2

Changelog:
	- Fix auditlog in case of internal redirect
	- Fix nginx sends response without headers
	- Fix nginx not clearing body cache
	- Fix config setting not respected: client_body_in_file_only on
	- Fix audit_log not generated for disruptive actions
	- Exit more gracefully if uri length is zero

Sponsored by:	Netzkommune GmbH

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Mark Broken on armv6

configuring additional dynamic modules
adding module in
/wrkdirs/usr/ports/security/modsecurity3-nginx/work/ModSecurity-nginx-1.0.1
checking for ModSecurity library ... not found
checking for ModSecurity library in /usr/local/modsecurity ... not found
 ./configure: error: ngx_http_modsecurity_module requires the ModSecurity
library.
===>  Script "configure" failed unexpectedly.

Sponsored by:	Netzkommune GmbH

Update NGINX version

PR:		246228
Sponsored by:	Netzkommune GmbH

Update modsecurity3-nginx to 1.0.1

PR:		243411 243412
Sponsored by:	Netzkommune GmbH

security/modsecurity3-nginx: fix build on GCC architectures

C11 compiler is needed because of typedef redefinitions.

MFH:		2020Q1 (fix build blanket)

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

Fix typo

Sponsored by:	Netzkommune GmbH

New Port: security/modsecurity-nginx

The ModSecurity-nginx connector is the connection point between Nginx and
libmodsecurity
(ModSecurity v3). Said another way, this project provides a communication
channel between Nginx
and libmodsecurity. This connector is required to use LibModSecurity with Nginx.

The ModSecurity-nginx connector takes the form of an Nginx module.
The module simply serves as a layer of communication between Nginx and
ModSecurity.

Notice that this project depends on libmodsecurity rather than ModSecurity
(version 2.9 or less).

WWW: https://github.com/SpiderLabs/ModSecurity-nginx

Sponsored by:	Netzkommune GmbH