Cool, thanks for the update!
Sven
On 23.01.20 20:19, Entropy wrote:
Okay, nevermind. I solved that by using a MutationObserver in javascript to
look for the thing Wicket makes visible or not and invoke my javascript as
needed.
--
Sent from:
Okay, nevermind. I solved that by using a MutationObserver in javascript to
look for the thing Wicket makes visible or not and invoke my javascript as
needed.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
Thank you, I'll try~
On Thu, Jan 23, 2020 at 5:30 PM NLogan wrote:
> To set SameSite only on JSESSIONID you can do
>
> *Header edit Set-Cookie ^(JSESSIONID.*)$ $1;HttpOnly;Secure;SameSite=None*
>
> It works for me
>
>
> Got the syntax from :
>
>
I just tried that and in terms of timing, it's perfect! However, my
front-end guys put together a multi-piece veil that blocks input, displays
our spinny, but also does some accessibility stuff and focus stuff that they
consider important. I'm going to go talk to them and see if they can live
To set SameSite only on JSESSIONID you can do
*Header edit Set-Cookie ^(JSESSIONID.*)$ $1;HttpOnly;Secure;SameSite=None*
It works for me
Got the syntax from :
https://stackoverflow.com/questions/53762523/setting-the-samesite-attribute-on-the-jsessionid-cookie-using-apache-config
