feat(http): configurable origin cookie#21
Merged
Conversation
| #sameSite: string; | ||
| #secure: boolean; | ||
|
|
||
| #httpOnly = 'HttpOnly'; |
Member
There was a problem hiding this comment.
Why is this a field if it's always a part of the cookie?
Member
Author
There was a problem hiding this comment.
I first had it as an input option, but then I removed it. Is this middleware prescriptive or not?
I decided that, as jitar plugins, we have a say in how things are done. That's why it is always part of the cookie, and it cannot get read by JavaScript.
If you agree, then I would also fix the path on /rpc, as that's the only endpoint towards Jitar.
petermasking
approved these changes
May 19, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #20
Changes proposed in this pull request:
Bumped version (Y/N) : Yes, to
0.1.5