raw url encoding csrf token (without padding =) #2248

Closed
opened 2025-11-02 04:29:25 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @beeonthego on GitHub (Aug 25, 2018).

I would like to change csrf token encoding to raw url encoding (without = padding), and reuse the csrf token as query string on some GET requests such as /logout.

This involves changing code in the vendor directory. Where should I submit the pr request? Should I submit to the upstream repo (go-macaron/csrf)

Originally created by @beeonthego on GitHub (Aug 25, 2018). I would like to change csrf token encoding to raw url encoding (without = padding), and reuse the csrf token as query string on some GET requests such as /logout. This involves changing code in the vendor directory. Where should I submit the pr request? Should I submit to the upstream repo (go-macaron/csrf)
GiteaMirror added the issue/stale label 2025-11-02 04:29:25 -06:00
Author
Owner

@techknowlogick commented on GitHub (Aug 25, 2018):

@beeonthego thanks for the PR. Please submit upstream, then once accepted you can update the dep file in Gitea

@techknowlogick commented on GitHub (Aug 25, 2018): @beeonthego thanks for the PR. Please submit upstream, then once accepted you can update the dep file in Gitea
Author
Owner

@beeonthego commented on GitHub (Aug 25, 2018):

great. thanks. will do that.

@beeonthego commented on GitHub (Aug 25, 2018): great. thanks. will do that.
Author
Owner

@stale[bot] commented on GitHub (Jan 12, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 12, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Feb 21, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 21, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2248