Closed pankajsoni19 closed 4 years ago
Just a note that this is going to need to be changed slightly. The same site config is a public enum so we can't just add a new case as that would need a major release
I am using code from my forked repo. So getting this merged is not a priority for me. Though this is actually a big change from how cookies are handled in chrome, safari, firefox, that this should be merged in one way or other soon.
We can't merge this as is for Vapor 3, we'd need to find a way that doesn't break public API. I've added this as a todo for 4 since we should be able to slip this in before official release there.
@tanner0101 given the changes to how we handle enums as public APIs in Vapor - can we merge this PR?
@0xTim yeah adding a case to this one should be fine. I'm more concerned about the change in default now actually. Will adding lax by default cause any issues?
@tanner0101 Looking at this link we should be fine - if no same site attribute is set it defaults to lax anyway
@tanner0101 Was that the right link? Also will the release bot handle Vapor 3 releases correctly?
Oops, no meant to paste this one: https://github.com/vapor/vapor/blob/master/.github/contributing.md#releases
And yup release bot should work for this. If not, I'll make the tag manually after.
@tanner0101 looks like release bot isn't enabled on this repo
release-bot is added at the organization level, so it runs on all vapor/* repos. Looks like it gave a 200 response for that webhook so must be a bug. I'll look into it.
Tagged this manually at https://github.com/vapor/http/releases/tag/3.4.0. Thanks!
Adds the none attribute to SameSite cookies (#376). This resolves vapor/vapor#375.
⚠️ This contains an additional case in a public enum which may cause a breaking change if you're switching on it