SSLProxyPeerName used in the Apache Configuration example is probably a typo for SSLProxyCheckPeerName

Search terms you've used

is:issue SSLProxyPeerName

Describe the bug

The NSS Apache configuration can't start because of an unknown SSLProxyPeerName configuration setting. This can be solved by using the correct setting SSLProxyCheckPeerName.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://solidproject.org//self-hosting/nss/apache
2. Follow the direction and start up the httpd
3. You get an error that SSLProxyPeerName is an unknown option

Expected behavior

The Apache server shouldn't complain about the provided options

Screenshots

Oct 04 15:40:04 bellow2.ugent.be httpd[9137]: Invalid command 'SSLProxyPeerName', perhaps misspelled or defined...ation

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: Server
• OS: CentOS Linux release 7.7.1908 (Core)

Open the Apache configuration example at https://solidproject.org//self-hosting/nss/apache and compare the documented directive with Apache's reported unknown option. Replace the incorrect SSLProxyPeerName setting with SSLProxyCheckPeerName, then verify that the example no longer causes the reported httpd startup error.