cancel
Showing results for 
Search instead for 
Did you mean: 

manipulating HostSecure and PortSecure

Former Member
0 Kudos

I have a situation identical to one that was described in note 744768. I have one Wgate and a service that switches between http and https and uses two domains "www.external.com" and "secure.external.com". The note's solution was to setup the hostsecure, portsecure, hostunsecure, portunsecure parameters in the service(i.e. on the agate side).

I've done this but I'm still running into a problem in that I get the "No service name specified" - "Session Already terminated" error when trying to browse from an SSL page to non-SSL page and vice-versa.

Has anyone had to deal with this?

Kevin.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Kevin

"No Service name specified" either means an URL did not include the '!'-sign or it could mean the ~session cookie for this URL is missing.

By default a session cookie usually is sent without a particular cookie-domain.

This means if you call first www.external.com you will receive a cookie for domain www.external.com and the browser is only allowed to return the ~session cookie to www.external.com, but not to secure.external.com.

Before changing the cookie-domain you could try if

~cookies=0

changes the behavior.

(if that is not possible there is also a way to change the cookie-domain)

best regards

Gerd

Answers (1)

Answers (1)

Former Member
0 Kudos

I added the service parameter "~cookie" to the service file and set it "0", and then switching between SSL and non-SSL worked.

Thank you!