Be careful if you have headers setting cookie params
-
I found that the thing that was stopping the plugin version 1.1.1 working was a http header I had set for security
Header always edit Set-Cookie ^(.*)$ “$1; HTTPOnly; Secure; SameSite=Strict
Perhaps that is a header others wouldn’t set.
Hopefully this will be helpful to someone else if they have the same issue. I don’t know if that is in the documentation.
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
The topic ‘Be careful if you have headers setting cookie params’ is closed to new replies.
