Add solution for Challenge 5 by Raycas96

[Raycas96]

Challenge 5 Solution

Submitted by: @Raycas96
Challenge: Challenge 5

Description

This PR contains my solution for Challenge 5.

Changes

• Added solution file to challenge-5/submissions/Raycas96/solution-template.go

Testing

• Solution passes all test cases
• Code follows Go best practices

Thank you for reviewing my submission! 🚀

[coderabbitai]

Walkthrough

A Go HTTP server implementation has been added with authentication middleware and two endpoint handlers. The AuthMiddleware validates requests via the X-Auth-Token header against a hardcoded "secret" token. The /hello endpoint is publicly accessible, while /secure requires authentication. The SetupServer function wires the routes.

Changes

Cohort / File(s)	Summary
HTTP Server with Authentication challenge-5/submissions/Raycas96/solution-template.go	Added AuthMiddleware that validates X-Auth-Token header, two HTTP handlers (helloHandler and secureHandler), SetupServer to register routes with middleware, and a validToken constant ("secret").

Sequence Diagram(s)

sequenceDiagram
    actor Client
    participant Server as HTTP Server
    participant AuthMW as AuthMiddleware
    participant SecureHandler as secureHandler

    rect rgba(0, 150, 0, 0.5)
    Note over Client,SecureHandler: Request with Valid Token
    Client->>Server: GET /secure<br/>X-Auth-Token: secret
    Server->>AuthMW: Check authentication
    AuthMW->>AuthMW: Validate token matches "secret"
    AuthMW->>SecureHandler: Token valid, forward request
    SecureHandler->>Client: 200 OK<br/>"You are authorized!"
    end

    rect rgba(150, 0, 0, 0.5)
    Note over Client,SecureHandler: Request without Token
    Client->>Server: GET /secure<br/>(no X-Auth-Token header)
    Server->>AuthMW: Check authentication
    AuthMW->>AuthMW: Token header missing
    AuthMW->>Client: 401 Unauthorized
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Add solution for Challenge 5 by Kosench #608: Adds identical Go HTTP handlers and AuthMiddleware implementation checking X-Auth-Token against "secret" token for the same challenge.
• Add solution for Challenge 5 by baindraraj #624: Implements the same Challenge 5 HTTP server scaffold with matching AuthMiddleware, SetupServer, and handler functions.
• Implementation of the middleware function that check all requests for valid token #1482: Introduces the same authentication middleware with X-Auth-Token validation and /hello//secure endpoint handlers.

Poem

🐰 A secret token guards the way,
AuthMiddleware checks each day,
/secure paths are now protected tight,
While /hello greets with pure delight!
Hoppy authentication hops just right! 🔐

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: submitting a solution for Challenge 5, which matches the added solution file in the changeset.
Description check	✅ Passed	The description is relevant to the changeset, explaining it's a Challenge 5 solution submission with clear details about the file added and testing status.
Docstring Coverage	✅ Passed	Docstring coverage is 80.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

challenge-5/submissions/Raycas96/solution-template.go (1)

18-18: Use validToken in the auth check and simplify the condition.

At Line [18], authHeader == "" || authHeader != "secret" is redundant and hardcodes the token literal again. Prefer a single comparison against validToken.

Proposed cleanup

-		if authHeader == "" || authHeader != "secret"  {
+		if authHeader != validToken {
 		    http.Error(w, "", http.StatusUnauthorized)
 		    return 
 		}

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d033ea28-ecca-4f0a-94ec-3830bd562571

📥 Commits

Reviewing files that changed from the base of the PR and between 6a002af and 4fd484c.

📒 Files selected for processing (1)

• challenge-5/submissions/Raycas96/solution-template.go

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Update the handler comment to avoid implying GET-only behavior.

Line [32] says “on GET /secure”, but this handler is correctly method-agnostic. Keeping the comment as-is can mislead future edits into adding method restrictions that would break expected behavior.

Based on learnings: In challenge-5/submissions/*/solution-template.go, ensure the secureHandler is method-agnostic (do not restrict it to GET), and tests include POST /secure with valid token expecting 200 OK.

[github-actions]

🎉 Auto-merged!

This PR was automatically merged after 2 days with all checks passing.

Thank you for your contribution, @Raycas96!