fix(iOS): fix 'secure' and 'httpOnly' values always being false #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@safaiyeh what do you think? 馃憖 |
|
Appreciate it! Lets ship it |
safaiyeh
pushed a commit
that referenced
this pull request
Aug 26, 2021
## [6.0.9](v6.0.8...v6.0.9) (2021-08-26) ### Bug Fixes * **iOS:** fix 'secure' and 'httpOnly' values always being false ([#126](#126)) ([354e9bb](354e9bb))
|
馃帀 This PR is included in version 6.0.9 馃帀 The release is available on: Your semantic-release bot 馃摝馃殌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
On iOS
set()method always stores cookies withsecureandhttpOnlybeingfalse. This PR fixes it.Possibly a breaking change for those, who assume they have been storing
secureandhttpOnlycookies.Fixes #38
Note: this is my first community PR ever. 馃槆
Type of change
Checklist