Unable update peronsal/repository/orgnization avatars #3832

Closed
opened 2025-11-02 05:27:23 -06:00 by GiteaMirror · 14 comments
Owner

Originally created by @pan3793 on GitHub (Aug 23, 2019).

I just use official managed server gitea.com, but when I update avatar of person or organization, always return error Bad Request: no CSRF token present

Originally created by @pan3793 on GitHub (Aug 23, 2019). I just use official managed server gitea.com, but when I update avatar of person or organization, always return error `Bad Request: no CSRF token present`
GiteaMirror added the issue/staletype/bug labels 2025-11-02 05:27:23 -06:00
Author
Owner

@HaoweiCh commented on GitHub (Aug 24, 2019):

save here, but only organization

@HaoweiCh commented on GitHub (Aug 24, 2019): save here, but only organization
Author
Owner

@lunny commented on GitHub (Aug 25, 2019):

If that's gitea.com instance problem but not gitea's, Please go to https://gitea.com/gitea/gitea.com/issues to file an issue.

@lunny commented on GitHub (Aug 25, 2019): If that's gitea.com instance problem but not gitea's, Please go to https://gitea.com/gitea/gitea.com/issues to file an issue.
Author
Owner

@HaoweiCh commented on GitHub (Aug 25, 2019):

gitea version: 1.8.3 built with go1.12.6 : bindata, sqlite, sqlite_unlock_notify

running in Docker...

I cannot update org avatar

@HaoweiCh commented on GitHub (Aug 25, 2019): `gitea version: 1.8.3 built with go1.12.6 : bindata, sqlite, sqlite_unlock_notify` running in Docker... I cannot update org avatar
Author
Owner

@pan3793 commented on GitHub (Aug 29, 2019):

close this, new issue move to https://gitea.com/gitea/gitea.com/issues/4

@pan3793 commented on GitHub (Aug 29, 2019): close this, new issue move to https://gitea.com/gitea/gitea.com/issues/4
Author
Owner

@lunny commented on GitHub (Aug 29, 2019):

I found that this is a bug of gitea but not a configuration error of gitea.com

@lunny commented on GitHub (Aug 29, 2019): I found that this is a bug of gitea but not a configuration error of gitea.com
Author
Owner

@lunny commented on GitHub (Aug 30, 2019):

I can reproduce this on macOS Chrome 76.
But I cannot reproduce this on macOS Firefox 68 and Safari 12.1.1

@lunny commented on GitHub (Aug 30, 2019): I can reproduce this on macOS Chrome 76. But I cannot reproduce this on macOS Firefox 68 and Safari 12.1.1
Author
Owner

@lunny commented on GitHub (Aug 30, 2019):

It should be related with serviceworker.

@lunny commented on GitHub (Aug 30, 2019): It should be related with serviceworker.
Author
Owner

@pan3793 commented on GitHub (Aug 30, 2019):

Ummm, I have only tested it on macOS Chrome before, now it seems that the temporary solution is just to use Safari to upgrade avatars.

@pan3793 commented on GitHub (Aug 30, 2019): Ummm, I have only tested it on macOS Chrome before, now it seems that the temporary solution is just to use Safari to upgrade avatars.
Author
Owner

@iHaPBoy commented on GitHub (Nov 29, 2019):

I found this bug on Chrome (macOS), only letters, numbers, and the "-" and "+" characters filename could uploaded.

@iHaPBoy commented on GitHub (Nov 29, 2019): I found this bug on Chrome (macOS), only **letters, numbers, and the "-" and "+" characters** filename could uploaded.
Author
Owner

@steadfasterX commented on GitHub (Dec 18, 2019):

I found this bug on Chrome (macOS), only letters, numbers, and the "-" and "+" characters filename could uploaded.

same here (Linux) but it affects also german Umlauts (äüö)

@steadfasterX commented on GitHub (Dec 18, 2019): > I found this bug on Chrome (macOS), only **letters, numbers, and the "-" and "+" characters** filename could uploaded. same here (Linux) but it affects also german Umlauts (äüö)
Author
Owner

@almindor commented on GitHub (Jan 15, 2020):

Same here on a fresh install on arch linux server using Brave browser

@almindor commented on GitHub (Jan 15, 2020): Same here on a fresh install on arch linux server using Brave browser
Author
Owner

@stale[bot] commented on GitHub (Mar 15, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 15, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (May 14, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 14, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (May 30, 2020):

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

@stale[bot] commented on GitHub (May 30, 2020): 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#3832