Add option -a, add possibility to manage ssl client profiles and vserver rules

1 files changed, 15 insertions, 1 deletions

diff --git a/docs/fapi.txt b/docs/fapi.txt
index 67fe651..8dea5c9 100644
--- a/docs/fapi.txt
+++ b/docs/fapi.txt
@@ -121,7 +121,7 @@ EXAMPLES
   Setting up simple HTTP NAT Services
     A simple HTTP NATed service can be created as follows.
 
-      fapi vserver myvserver.example.com:80 create PROTOCOL_TCP /Common/http
+      fapi vserver myvserver.example.com:80 create PROTOCOL_TCP http
       fapi vserver myvserver.example.com:80 set vlan VLANNAME
       fapi vserver myvserver.example.com:80 set pool foopool
 
@@ -137,6 +137,20 @@ EXAMPLES
 
       fapi vserver myvserver.example.com:80 set snat automap
 
+  Settung up simple SNAT Services with SSL offloading enabled
+    Just like SNAT service (use port 443) but with these additional steps
+
+    First Upload the SSL certificate to the F5 BIG IP (e.g. System -> File
+    Management -> SSL Certificate List on BIG IP V11.4).
+
+      # Afterwards create a new SSL profile to use the new certificate:
+      # (Will automatically use key/crt myserver.example.com.{key,crt})
+      fapi profileclientssl myserver.example.com create
+
+      # Then attach that profile to the vserver (default context is 
+      # PROFILE_TYPE_CLIENT_SSL, which means SSL between F5 and Clients)
+      fapi vserver myvserver.example.com:443 profile add myserver.example.com
+
   About the NAME argument
     In most cases NAME can be a hostname, FQDN or an IP address. Optionally
     folled by a port: