Skip to content
New issue

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

Allow CSRF-token to be a function #393

Closed
wants to merge 1 commit into from

Conversation

eneroth
Copy link

@eneroth eneroth commented Nov 3, 2021

  • This modifies make-channel-socket-client!.
  • When the function is evaluated, it's expected to return a CSRF-token.
  • CSRF-token strings are still supported.

This is in reference to #351.

- This modifies `make-channel-socket-client!`.
- When the function is evaluated, it's expected to return a CSRF-token.
- CSRF-token strings are still supported.
@eneroth
Copy link
Author

eneroth commented Nov 3, 2021

Note @ptaoussanis, I can update the relevant sections in the readme as well, I just wanted to get your feedback on this before proceeding.

@ptaoussanis
Copy link
Member

@eneroth Hi Henrik, thanks a lot for this! Merging manually now. Apologies for the long delay getting this in!

ptaoussanis pushed a commit that referenced this pull request May 31, 2022
- This modifies `make-channel-socket-client!`.
- When the function is evaluated, it's expected to return a CSRF-token.
- CSRF-token strings are still supported.
ptaoussanis pushed a commit that referenced this pull request May 31, 2022
- This modifies `make-channel-socket-client!`.
- When the function is evaluated, it's expected to return a CSRF-token.
- CSRF-token strings are still supported.
ptaoussanis pushed a commit that referenced this pull request Jun 1, 2022
…sanis)

- This modifies `make-channel-socket-client!`.
- When the function is evaluated, it's expected to return a CSRF-token.
- CSRF-token strings are still supported.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants