@jaitaiwan #276 (review)

Sure I can add Samesite as None. However, some browsers are mandating additional Secure attribute when SameSite=None.
( chrome, firefox )

I think it will be good to add Secure along with SameSite=None, let me know what you think!

I think that's a good idea. We can release it under a major version tag so it doesn't break folk's installations either way.

LGTM - Just waiting for scanning/tests to finish

@jaitaiwan I believe vulncheck issues are unrelated and we can tackle them separately.
Also, I ran linter locally and I don't see issues which are somehow reported in github workflow.

docker run -t --rm -v $(pwd):/app -w /app golangci/golangci-lint:v1.53.3 golangci-lint run -v

Can you help?

The linter is passing for me as well. I think this could be a false positive, I can't even find the existence of max reported in the error.
I think we can ignore the lint errors, and as @bharat-rajani mentioned we can work through the vuln failures seperately. @jaitaiwan WDYT?

We'll merge this once we've fixed #277 I think

I think this might be missing from v1.4.0 can you check @bharat-rajani or @apoorvajagtap ?

@jaitaiwan the new default None, like what @bharat-rajani has mentioned, breaks setup where they disable Secure (e.g. local HTTP server) . it's an easy fix but I thought it was planned for a major version bump (or at least, mentioned in release notes)