SESCOOKIENOSEC (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 8: | Line 8: | ||
'''Note:''' It is probably a bad idea to transmit a session cookie on a non-SSL connection, because someone who spies the session cookie can use it to perform trusted logins on the ''[[Janus Web Server]]'' port (though such a person cannot determine any password associated with the session cookie). | '''Note:''' It is probably a bad idea to transmit a session cookie on a non-SSL connection, because someone who spies the session cookie can use it to perform trusted logins on the ''[[Janus Web Server]]'' port (though such a person cannot determine any password associated with the session cookie). | ||
<var>SESCOOKIENOSEC</var> is valid only for WEBSERV ports. | <var>SESCOOKIENOSEC</var> is valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | ||
==See also== | ==See also== | ||
Revision as of 23:19, 28 February 2012
<section begin="desc" />Send the session cookie 'unsecured'.<section end="desc" />
SESCOOKIENOSEC is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.
Indicates that the cookie specified by SESCOOKIE will not be sent to the browser as a "secure" cookie. This makes it possible with some browsers in certain situations to use the SESCOOKIE cookie to have a logical session operate over multiple Janus Web Server ports.
Note: It is probably a bad idea to transmit a session cookie on a non-SSL connection, because someone who spies the session cookie can use it to perform trusted logins on the Janus Web Server port (though such a person cannot determine any password associated with the session cookie).
SESCOOKIENOSEC is valid only for WEBSERV ports.