Re: cannot use gitlab,
Posted: 2024-04-18, 18:40
it seems gitlab.com's default action is to ask users to log in if a project hits a 404. Most likely this is just because they throw a 404 for "protected"/"private" repos and they just wholesale redirect to the login in case a logged in account would grant access. That's probably a gitlab.com specific thing (maybe hinting at it being made administrator-eyes-only by staff or something, and not actually being "gone"...)
This has nothing to do with the cloudlflare challenge though, which sits before all that and is not handled on gitlab.com's server. That challenge passes just fine, by the way, but it may not like your configuration, e.g. if you're blocking scripts or what not.
This has nothing to do with the cloudlflare challenge though, which sits before all that and is not handled on gitlab.com's server. That challenge passes just fine, by the way, but it may not like your configuration, e.g. if you're blocking scripts or what not.