mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 06:25:54 +03:00
[GH-ISSUE #613] Unable to delete account in web interface #318
Labels
No labels
component:backend
component:builds
component:builds
component:extension
component:frontend
component:readability
database
database:mysql
database:postgres
database:sqlite
feature:ebooks
github_actions
good first issue
hacktoberfest
note:duplicate?
note:fixed?
note:out-of-scope?
os:windows
priority:high
priority:low
pull-request
resolution:as-intended
resolution:cant-reproduce
resolution:duplicate
resolution:fixed
resolution:wontfix
tag:TBD
tag:big-task
tag:help-wanted
tag:huge-data
tag:meta
tag:more-info
tag:next
tag:no-stale
tag:requires-migrations
tag:research
tag:security 🛡️
tag:stale
tag:waiting-for-assignee
type:bug
type:documentation
type:enhancement
type:meta
type:ux
user:cli
user:web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shiori#318
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @kolatv23 on GitHub (May 28, 2023).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/613
Data
Describe the bug / actual behavior
In shiori web UI, 'Delete account' button always returns a '404' error message.
Expected behavior
Clicking on 'Delete account' button should delete selected account.
To Reproduce
Steps to reproduce the behavior:
Notes
I found out the problem is in web interface: there is no session-id in request headers, add it to the headers should fix the problem.
@l0b0 commented on GitHub (Oct 11, 2023):
I'm getting a slightly different error for this:
@fmartingr commented on GitHub (May 25, 2024):
I have tested this in 1.6.3 and it's working correctly. Closing this issue.
@l0b0 If you are experiencing the issue in the latest version, can you fill a new bug with more details? I see that you are using NGINX as reverse proxy so please check that the configuration of the proxy is allowing you that first. Thank you!
@l0b0 commented on GitHub (May 26, 2024):
FYI, I'm no longer using Shiori.