github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-10 05:32:52 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

COOKIE_SECURE doesn't flag _csrf cookie as 'Secure' #715

New Issue
Closed
opened 2025-11-02 03:33:57 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 03:33:57 -06:00
Owner
Copy Link

Originally created by @eripa on GitHub (May 16, 2017).

  • Gitea version (or commit ref): 1.1.1
  • Git version: 2.1.4
  • Operating system: Debian GNU/Linux 8.8 (jessie) x86_4
  • Database:
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I was under the impression that setting COOKIE_SECURE to true will make all cookies have the 'Secure' flag set. However it only seem to apply to the i_like_gitea cookie.

https://try.gitea.io doesn't seem to be configured with COOKIE_SECURE.

Originally created by @eripa on GitHub (May 16, 2017). - Gitea version (or commit ref): 1.1.1 - Git version: 2.1.4 - Operating system: Debian GNU/Linux 8.8 (jessie) x86_4 - Database: - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description I was under the impression that setting COOKIE_SECURE to true will make all cookies have the 'Secure' flag set. However it only seem to apply to the i_like_gitea cookie. https://try.gitea.io doesn't seem to be configured with COOKIE_SECURE.
GiteaMirror added the topic/security label 2025-11-02 03:33:57 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/security
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#715
Delete Branch "%!s()"

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?