- Mar 18, 2020
-
-
GitLab Bot authored
-
- Mar 12, 2020
-
-
GitLab Bot authored
-
- Mar 05, 2020
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Mar 02, 2020
-
-
GitLab Bot authored
-
- Feb 05, 2020
-
-
GitLab Bot authored
-
- Feb 04, 2020
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Jan 30, 2020
-
-
GitLab Bot authored
-
- Jan 29, 2020
-
-
GitLab Bot authored
-
- Jan 23, 2020
-
-
GitLab Bot authored
-
- Jan 03, 2020
-
-
GitLab Bot authored
-
- Dec 16, 2019
-
-
GitLab Bot authored
-
- Dec 13, 2019
-
-
GitLab Bot authored
-
- Dec 12, 2019
-
-
GitLab Bot authored
-
- Dec 11, 2019
-
-
GitLab Bot authored
-
- Dec 03, 2019
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Nov 18, 2019
-
-
GitLab Bot authored
-
- Nov 17, 2019
-
-
GitLab Bot authored
-
- Nov 13, 2019
-
-
GitLab Bot authored
-
- Nov 12, 2019
-
-
GitLab Bot authored
-
- Nov 08, 2019
-
-
GitLab Bot authored
-
GitLab Bot authored
-
GitLab Bot authored
-
GitLab Bot authored
-
- Nov 07, 2019
-
-
GitLab Bot authored
-
- Oct 25, 2019
-
-
GitLab Bot authored
-
- Oct 18, 2019
-
-
GitLab Bot authored
-
- Oct 10, 2019
-
-
GitLab Bot authored
-
- Oct 09, 2019
-
-
Kerri Miller authored
This method, #route_not_found, is executed as the final fallback for unrecognized routes (as the name might imply.) We want to avoid `#authenticate_user!` when calling `#route_not_found`; `#authenticate_user!` can, depending on the request format, return a 401 instead of redirecting to a login page. This opens a subtle security exploit where anonymous users will receive a 401 response when attempting to access a private repo, while a recognized user will receive a 404, exposing the existence of the private, hidden repo.
-
- Oct 01, 2019
-
-
GitLab Bot authored
-
- Sep 28, 2019
-
-
GitLab Bot authored
-
- Sep 26, 2019
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Sep 13, 2019
-
-
GitLab Bot authored
-
- Aug 31, 2019
-
-
dineshpanda authored
-
- Aug 15, 2019
-
-
George Koltsov authored
-
- Aug 14, 2019
-
-
George Koltsov authored
-
- Aug 08, 2019
-
-
Alex Buijs authored
-