3 Drawback solely on Firefox:
- some cookies incorrectly use the beneficial attribute “SameSite”
- some cookies had been rejected as a result of they’ve already expired
- most essential : consumer will not be logged out as a result of wordpress_logged_in_ will not be deleted
1 – These issues solely seems on firefox console however appears to be official to guard towards CSRF assaults.
Is it a browser downside or is WordPress simply not updated with model 6.0.1?
Is there an present php code so as to add to all wordpress cookies the samecookie attribute and add a desired or default worth “none”?
2 – Additionally on 4 cookies generated by wordpress to authenticate a consumer I get 17 warnings of “cookies rejected as a result of they’ve already expired”.
wordpress_,
wordpress_sec_,
wordpress_logged_in_,
wp-settings-0,
wp-settings-time-0,
wordpressuser_,
wordpresspass_,
wordpressuser_,
wp-postpass_
These warnings come all from admin-ajax.php
some cookie have warnings a number of occasions, nonetheless the consumer is logged in and wp cookies are properly generated.
how I can resolved this warnings ?
3- Final however not least, solely Firefox doesn’t delete (wordpress_logged_in_ cookie) the consumer authentication cookie on logout (wp_logout). Is it associated to the issues talked about above?
Is that this associated to a cookie path downside regardless of different browsers having no downside logging out the consumer?
How can I correctly delete this cookie even after wp_logout_url(get_permalink())?
thanks in your assist