PWA Development

[de la Rosa]

Hi Jane,

It sure does look like painfully heading that way. Will have to start checking it out.

Thanks,
Vic

[Bruce]

Jane is completely correct - there's is a (sophisticated) approach to the issue - hopefully we can convince her to do a webinar on the subject )

>> I understand, for this particular customer(it's not a bank)

ahh - we'll that's a relief at least - I'm not sure where I got the idea it was a bank - but certainly not-a-bank is less disturbing...

>> Btw, does the https security protocols already apply on the Socket level?

It's at the "connection" level - yes.

>> added the ServerSettings tab,

make sure the settings in the WebServer Extension template are "using" the settings template. In other words;

General Tab:

Host Names (CSL): Set:Domains
Listen on Secure Port: set:SecurePort
Listen on Insecure Port: set:InsecurePort

Advanced Tab
Session Timeout: set:SessionTimeout

[Jane]

"Sophisticated"    I like the sound of that... 

Vic,

Here are  links that give more information on this trick:

http://www.petenetlive.com/KB/Article/0000830

https://community.spiceworks.com/topic/566556-ssl-certificates-internal-use-and-external-use



jf

[de la Rosa]

Hi Bruce,

>>make sure the settings in the WebServer Extension template are "using" the settings template. In other words;

>>General Tab:

>>Host Names (CSL): Set:Domains
>>Listen on Secure Port: set:SecurePort
>>Listen on Insecure Port: set:InsecurePort

>>Advanced Tab
>>Session Timeout: set:SessionTimeout

Yes, those settings were the cause of the issue and behavior.

Thanks,
Vic

[de la Rosa]

Hi Jane,

Thanks for sharing the links to your sophisticated trick. 

Vic