We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On WACookie, #writeOn:, through #rfc6265String, writes out ‘Max-Age’ and ‘SameSite’ attributes:
#writeOn:
#rfc6265String
Seaside/repository/Seaside-Core.package/WACookie.class/instance/rfc6265String.st
Lines 2 to 16 in c152487
But on WAFastCGIAdaptor, #addCookie:toStream: does not write out those attributes:
#addCookie:toStream:
Seaside/repository/Seaside-Adaptors-FastCGI.package/WAFastCGIAdaptor.class/instance/addCookie.toStream..st
Lines 12 to 17 in c152487
I’m not sure why it doesn’t just use the WACookie’s #writeOn:.
The text was updated successfully, but these errors were encountered:
The change to rfc6265 was never properly implemented in the FastCGI adapter. The current code is there because of #1115
It seems we should indeed simply call writeOn: and remove the old code.
writeOn:
Sorry, something went wrong.
In #1378, I call the rfc6265String because this is also the method being used in the Zinc Adapter.
rfc6265String
Successfully merging a pull request may close this issue.
On WACookie,
#writeOn:
, through#rfc6265String
, writes out ‘Max-Age’ and ‘SameSite’ attributes:Seaside/repository/Seaside-Core.package/WACookie.class/instance/rfc6265String.st
Lines 2 to 16 in c152487
But on WAFastCGIAdaptor,
#addCookie:toStream:
does not write out those attributes:Seaside/repository/Seaside-Adaptors-FastCGI.package/WAFastCGIAdaptor.class/instance/addCookie.toStream..st
Lines 12 to 17 in c152487
I’m not sure why it doesn’t just use the WACookie’s
#writeOn:
.The text was updated successfully, but these errors were encountered: