From 8b86df37526d864200b7b29953e6d9d98343e1f0 Mon Sep 17 00:00:00 2001
From: Scott Ullrich <sullrich@pfsense.org>
Date: Fri, 7 Dec 2007 19:35:35 +0000
Subject: 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(-)

(limited to 'usr/local/www')

diff --git a/usr/local/www/services_captiveportal.php b/usr/local/www/services_captiveportal.php
index adc7e4a..30c9ed0 100755
--- a/usr/local/www/services_captiveportal.php
+++ b/usr/local/www/services_captiveportal.php
@@ -528,7 +528,7 @@ value="<?=htmlspecialchars($pconfig['radiuskey2']);?>"></td>
       <td valign="top" class="vncell">HTTPS server name </td>
       <td class="vtable">
         <input name="httpsname" type="text" class="formfld unknown" 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>
-- 
cgit v1.1