Re: SSL and public facing web site on the i

Brad,

No I'm not being cheeky in this case. I normally don't attempt humor on
the list, as it's hard to be good at it.

Yes, of course you can use a text editor to add the SSL directives to the
config file. The GUI is not required. But how about doing a test? Remove or
add the SSLAppName directive using an editor, then go to DCM to see if your
changes are reflected there. In my case, editing the HTTP configuration has
no affect on the application list found in DCM.

Then try the following:

Use the GUI -> Security screens to add or remove SSL directives. Then
return to DCM to see the changes in the applications list.

It appears that the HTTP Admin GUI is somehow updating the applications
list shown in the DCM.

Other than that, I'm with you, preferring to use a text editor to modify
the HTTP configuration file.

-Nathan.



----- Original Message -----
From: Bradley Stone <bvstone@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Cc:
Sent: Tuesday, April 23, 2013 1:42 PM
Subject: Re: SSL and public facing web site on the i

I don't know if you were being cheeky here or not. :) Those directives are
required, and they can easily be added by editing the config file.

You just have to make sure that the name you use on SSLAppName matches the
name assigned to the certificate (which you do in DCM).
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.