scott001 Posted May 2, 2019 Report Posted May 2, 2019 Is there a setting to make my cookies secure, as currently they are not secure: The following Cookies are not secure, you should add the Secure instruction in the Set-Cookie HTTP header: www.celiac.com/adserv/www/delivery/lg.php?banner[...]celiacs%2F&cb=f3814766b9 set-cookie: spcsrf=58357e9856fb6e2fa93de7f9cdfc37e6; Expires=Thu, 02-May-19 23:52:50 GMT; Path=/; HttpOnly; SameSite=Strict set-cookie: UTGv2=D-h4c33fdc6d399b6de8496e40aa580775b642; Expires=Fri, 01-May-20 21:52:50 GMT; Path=/ https://www.celiac.com/adserv/www/delivery/asyncjs.php set-cookie: spcsrf=6520eb79b20bf2806ff4d56baf063477; Expires=Thu, 02-May-19 23:52:48 GMT; Path=/; HttpOnly; SameSite=Strict set-cookie: UTGv2=D-h42c4ac14766f5128084800ade37ed3e0344; Expires=Fri, 01-May-20 21:52:48 GMT; Path=/ Quote
scott001 Posted May 9, 2019 Author Report Posted May 9, 2019 I am still hoping for a solution to my insecure cookie issue. Revive is the only app on my domain that has this issue. All other apps have secure cookies. Quote
andrewatfornax Posted June 7, 2019 Report Posted June 7, 2019 I think the short answer is that I am not aware of any option to change this. Can you please raise a GitHub case (with PR if you are so inclined)? Quote
Artistan Posted February 3, 2020 Report Posted February 3, 2020 looks like this may be fixed in Revive Adserver 5.0.4 andrewatfornax 1 Quote
Pedro Braconnot Posted May 13, 2020 Report Posted May 13, 2020 I am having this issue with 5.0.5 Quote
Pedro Braconnot Posted May 13, 2020 Report Posted May 13, 2020 Chrome states that options should be SameSite=None Secure Error A cookie associated with a cross-site resource at http://example.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032. Quote
katana99 Posted May 29, 2020 Report Posted May 29, 2020 On 5/13/2020 at 7:08 PM, Pedro Braconnot said: I am having this issue with 5.0.5 im too, this huge problem is still not fixed... Quote
analogged Posted August 15, 2020 Report Posted August 15, 2020 Has there been any update to this or work around? I just updated to 5.0.5 as seen from someone in another thread with this issue but its still there. Quote
stapel_eliz Posted September 28, 2021 Report Posted September 28, 2021 Did this work in 5.0.4, but now is broken in 5.0.5? Because it kinda looked like things were going okay earlier in 2020...? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.