Can I assume that the Set-Cookie is the creation of a new session? Odd that is the example.
[ ~]$ curl -i --cookie "cookie-name=MTUxNjY3NTcxN3xEdi1CQkFFQ180SUFBUkFCRUFBQUpmLUNBQUVHYzNSeWFXNW5EQThBRFdGMWRHaGxiblJwWTJGMFpXUUVZbTl2YkFJQ0FBRT18M0_ZIEv6dOYHWKyD3GdEJhqUM8KvUJN-i4KIu7opWJA=;" http://localhost:8080/logout HTTP/1.1 200 OK Set-Cookie: cookie-name=MTUxNjc1ODc4MXxEdi1CQkFFQ180SUFBUkFCRUFBQUpmLUNBQUVHYzNSeWFXNW5EQThBRFdGMWRHaGxiblJwWTJGMFpXUUVZbTl2YkFJQ0FBQT18kAW2EKqIy_TFCZ9cXZTmfpnYrEmCfGzKJ-FYKa0O9Vs=; Path=/; Expires=Fri, 23 Feb 2018 01:53:01 GMT; Max-Age=2592000 Date: Wed, 24 Jan 2018 01:53:01 GMT Content-Length: 0 Content-Type: text/plain; charset=utf-8 Another question - where does gorilla store the session files on a Mac. Looking at the session source code, it gets the TMPDIR from the environment to create the session file, which gets deleted when I exit the program. However, when I restart the server, and I call the /secret endpoint, I still get the secret message rather than forbidden. Any ideas ? Is it actually being cached somewhere ? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
