Wim e91229eefb Respond with a 401 on git push when password isn't changed yet (#20026) ... If the user-agent starts with git and user must change password but hasn't return a 401 with the message. It must be a 401, git doesn't seem to show the contents of the error message when we return a 403 Fixes #19090		2022-06-19 20:23:00 +01:00
..
access_log.go
api.go	Call MultipartForm.RemoveAll when request finishes (#19606)	2022-05-05 16:13:23 +02:00
api_org.go	Move organization related structs into sub package (#18518)	2022-03-29 14:29:02 +08:00
api_test.go
auth.go	Respond with a 401 on git push when password isn't changed yet (#20026)	2022-06-19 20:23:00 +01:00
captcha.go
context.go	Call MultipartForm.RemoveAll when request finishes (#19606)	2022-05-05 16:13:23 +02:00
csrf.go	Refactor CSRF protection modules, make sure CSRF tokens can be up-to-date. (#19337)	2022-04-08 13:21:05 +08:00
form.go
org.go	Only show accessible teams in dashboard dropdown list (#19642)	2022-05-07 17:49:43 +02:00
package.go	Fix org package owner permissions (#19742)	2022-05-19 17:56:45 +02:00
pagination.go	Remove tab/TabName usage where it's not needed (#19973)	2022-06-15 23:05:32 +08:00
permission.go	Move access and repo permission to models/perm/access (#19350)	2022-05-11 12:09:36 +02:00
private.go	Call MultipartForm.RemoveAll when request finishes (#19606)	2022-05-05 16:13:23 +02:00
repo.go	Return 404 when tag is broken (#20017)	2022-06-18 19:08:34 +02:00
response.go
utils.go	Never use /api/v1 from Gitea UI Pages (#19318)	2022-04-07 20:59:56 +02:00
xsrf.go	Refactor CSRF protection modules, make sure CSRF tokens can be up-to-date. (#19337)	2022-04-08 13:21:05 +08:00
xsrf_test.go	Refactor CSRF protection modules, make sure CSRF tokens can be up-to-date. (#19337)	2022-04-08 13:21:05 +08:00