Send the deploy token via Authorization header, not the URL query #1
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
leon/Forge-Pages-Action!1
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/security-hardening"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The token was appended to the deploy URL as ?access_token=..., which leaks it into server, reverse-proxy, and CI logs. Send it in an Authorization: Bearer header instead.
Repo/protect/additional_base_path stay as query parameters (they are not secret).
Contributed by Michal Bielicki.
This is definitely a useful addition. I will merge it once Forge-Pages supports the token to be sent as a Bearer token.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.