Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
2343 posts
|
Hi all,
I have an application that has a Cookie based tracking strategy, but given that the SameSite setting is hardcoded to be 'Strict' it forbids (and actually breaks) the behavior of my Seaside app when it is embedded into an <iframe> in a third party domain. Should this SameSite setting be configurable somehow? The only way I found to do this was by subclassing the tracking strategy class. Regards, Esteban A. Maringolo _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
1618 posts
|
Hi Esteben,
Interesting case. I guess we didn't think about that. Usually you wouldn't want to share the tracking cookie with another domain but that might be a valid case This should probably be solved by updating the configurations (which can be tough), so if you feel up to it we'd appreciate a PR with such a change. Cheers, Max On 28 Nov 2020, at 19:25, Esteban Maringolo wrote: > Hi all, > > I have an application that has a Cookie based tracking strategy, but > given that the SameSite setting is hardcoded to be 'Strict' it forbids > (and actually breaks) the behavior of my Seaside app when it is > embedded into an <iframe> in a third party domain. > > Should this SameSite setting be configurable somehow? > > The only way I found to do this was by subclassing the tracking strategy class. > > Regards, > > Esteban A. Maringolo > _______________________________________________ > seaside-dev mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev ... [show rest of quote] ... [show rest of quote] _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
2343 posts
|
Hi Max,
I'll create the issue, at least as a reminder. Regards! Esteban A. Maringolo On Tue, Dec 1, 2020 at 5:18 PM Max Leske <[hidden email]> wrote: > > Hi Esteben, > > Interesting case. I guess we didn't think about that. Usually you wouldn't want to share the tracking cookie with another domain but that might be a valid case > > This should probably be solved by updating the configurations (which can be tough), so if you feel up to it we'd appreciate a PR with such a change. > > > Cheers, > Max > > On 28 Nov 2020, at 19:25, Esteban Maringolo wrote: > > > Hi all, > > > > I have an application that has a Cookie based tracking strategy, but > > given that the SameSite setting is hardcoded to be 'Strict' it forbids > > (and actually breaks) the behavior of my Seaside app when it is > > embedded into an <iframe> in a third party domain. > > > > Should this SameSite setting be configurable somehow? > > > > The only way I found to do this was by subclassing the tracking strategy class. > > > > Regards, > > > > Esteban A. Maringolo > > _______________________________________________ > > seaside-dev mailing list > > [hidden email] > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > _______________________________________________ > seaside-dev mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev ... [show rest of quote] _______________________________________________
seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Free forum by Nabble | Edit this page |