From 797661ab9bc3ddaea08c3089c2ae987e552e4dc6 Mon Sep 17 00:00:00 2001 From: Patrick Britton Date: Mon, 16 Feb 2026 22:49:42 -0600 Subject: [PATCH] fix: move ALTCHA endpoints to correct v1 group location - Move test and ALTCHA endpoints inside the v1 group where they belong - Fix route registration issue by placing routes in correct scope - Both auth and admin ALTCHA challenge endpoints should now work --- go-backend/cmd/api/main.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/go-backend/cmd/api/main.go b/go-backend/cmd/api/main.go index 8384b40..5b9bb10 100644 --- a/go-backend/cmd/api/main.go +++ b/go-backend/cmd/api/main.go @@ -262,13 +262,13 @@ func main() { } // Test endpoint to verify routing - r.GET("/api/v1/test", func(c *gin.Context) { + v1.GET("/test", func(c *gin.Context) { c.JSON(200, gin.H{"message": "Route test successful"}) }) - // ALTCHA challenge endpoint (no rate limiting) + // ALTCHA challenge endpoints (no rate limiting) v1.GET("/auth/altcha-challenge", authHandler.GetAltchaChallenge) - r.GET("/api/v1/admin/altcha-challenge", adminHandler.GetAltchaChallenge) + v1.GET("/admin/altcha-challenge", adminHandler.GetAltchaChallenge) authorized := v1.Group("") authorized.Use(middleware.AuthMiddleware(cfg.JWTSecret, dbPool))