Not. What the setting does is that it sends a 'Secure' parameter when setting the cookie. After receiving a cookie with this parameter, the client should only send it to the server when the connection used is secure.
This is why the client does not send the cookie back and you do not see it. In addition, the server should not send this type of cookie over an insecure connection.
See RFC-2109 , section 4.2.2 for an explanation of how the 'Secure' attribute is used and interpreted.
source share