Skip to content

issues/179 Add option to use base64 URL-safe encoding format for CSRF token #180

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

issues/179 Add option to use base64 URL-safe encoding format for CSRF token #180

wants to merge 2 commits into from

Conversation

Sang-Hyuk
Copy link

@Sang-Hyuk Sang-Hyuk commented Dec 6, 2024 •
edited
Loading

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update
  • Go Version Update
  • Dependency Update

Description

Related Tickets & Documents

Added/updated tests?

  • Yes
  • No, and this is why: please replace this line with details on why tests
    have not been included
  • I need help with writing tests

Run verifications and test

  • make verify is passing
  • make test is passing

@Sang-Hyuk Sang-Hyuk changed the title Add option to use base64 URL-safe encoding format for CSRF token [Issue-179] Add option to use base64 URL-safe encoding format for CSRF token Dec 6, 2024
@Sang-Hyuk Sang-Hyuk changed the title [Issue-179] Add option to use base64 URL-safe encoding format for CSRF token Issues/179 Add option to use base64 URL-safe encoding format for CSRF token Dec 9, 2024
@Sang-Hyuk Sang-Hyuk changed the title Issues/179 Add option to use base64 URL-safe encoding format for CSRF token issues/179 Add option to use base64 URL-safe encoding format for CSRF token Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
size/M
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Sang-Hyuk