From 0e4e011d63abbf0ec07417575d9820f73b5dd69a Mon Sep 17 00:00:00 2001
From: h-town <29696865+h-town@users.noreply.github.com>
Date: Sun, 29 Dec 2019 04:27:47 +0000
Subject: [PATCH] Clarify purpose of ID httpserver.ca

The existing description of "CA Certificate" is confusing, in that it implies the user should select the Certificate Authority responsible for generating their SSL pem (e.g. LetsEncrypt), when the parameter is solely used to specify the CA used for verifying Client Certificates. While this might be acceptable in self-signed scenarios where users have the appropriate keys to generate a client CA, it's unfortunately not the case for production SSL certs.
---
 .../mvc/app/controllers/OPNsense/Nginx/forms/httpserver.xml     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/nginx/src/opnsense/mvc/app/controllers/OPNsense/Nginx/forms/httpserver.xml b/www/nginx/src/opnsense/mvc/app/controllers/OPNsense/Nginx/forms/httpserver.xml
index 87e9c89161..62b3f44d65 100644
--- a/www/nginx/src/opnsense/mvc/app/controllers/OPNsense/Nginx/forms/httpserver.xml
+++ b/www/nginx/src/opnsense/mvc/app/controllers/OPNsense/Nginx/forms/httpserver.xml
@@ -94,7 +94,7 @@
   </field>
   <field>
     <id>httpserver.ca</id>
-    <label>CA Certificate</label>
+    <label>Client CA Certificate</label>
     <type>dropdown</type>
   </field>
   <field>