From ac8d9e8973744fdead2cf18b15aa00f4bf508717 Mon Sep 17 00:00:00 2001
From: Scott Ullrich <sullrich@pfsense.org>
Date: Fri, 7 Dec 2007 19:35:28 +0000
Subject: [PATCH] Clarify that the httpsname should resolve to the correct
 interface ip on the captive portal interface.

---
 usr/local/www/services_captiveportal.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/usr/local/www/services_captiveportal.php b/usr/local/www/services_captiveportal.php
index 09fe92ae47..01237c62df 100755
--- a/usr/local/www/services_captiveportal.php
+++ b/usr/local/www/services_captiveportal.php
@@ -527,7 +527,7 @@ to access after they've authenticated.</td>
       <td valign="top" class="vncell">HTTPS server name </td>
       <td class="vtable">
         <input name="httpsname" type="text" class="formfld" id="httpsname" size="30" value="<?=htmlspecialchars($pconfig['httpsname']);?>"><br>
-    This name will be used in the form action for the HTTPS POST and should match the Common Name (CN) in your certificate (otherwise, the client browser will most likely display a security warning). Make sure captive portal clients can resolve this name in DNS. </td>
+    This name will be used in the form action for the HTTPS POST and should match the Common Name (CN) in your certificate (otherwise, the client browser will most likely display a security warning). Make sure captive portal clients can resolve this name in DNS and verify on the client that the IP resolves to the correct interface IP on pfSense.. </td>
 	  </tr>
 	<tr>
       <td valign="top" class="vncell">HTTPS certificate</td>