What specific types of redirect errors does this skill resolve?

This skill identifies and resolves infinite 301/302 redirect cycles, conflicts between HTTP/HTTPS canonical logic, and misconfigured 'X-Forwarded-Proto' headers often found in load-balanced environments.

Which AI agents or development environments are compatible with this tool?

The skill is designed to work within any AI agent workspace that has access to code repositories or server configuration files, such as Nginx, Apache, or Express.js environments.

How do I set up the skill to analyze my specific server configuration?

No complex installation is required; simply provide the skill with access to your workspace or specific error logs, and it will begin the diagnostic process immediately.

What deliverables are included with the purchase of this skill?

You receive the full diagnostic workflow, a set of bounded repair actions, and a deterministic validation protocol to ensure the fix doesn't break existing security boundaries.

Can this skill handle redirect loops caused by authentication middleware or OAuth flows?

Yes, the skill is designed to handle complex authentication-triggered redirects, ensuring that login-related loops are repaired without compromising your security or authorization protocols.

Repair HTTP Redirect Loops & Navigation Bugs

FAULT BOUNDARY IDENTIFIED

Case analyzed

Behind a TLS-terminating reverse proxy, the app sees http internally and redirects every request to https. The proxy already serves https but does not rewrite the internal scheme, so /login alternates between the proxy's https URL and the app's canonicalization middleware until the browser reports too many redirects.

The supplied facts are sufficient to perform a concrete repair diagnosis for this case. No repository, production, vendor, or legal access is assumed.

Verified evidence

VERIFIED: TLS terminates at the reverse proxy.
VERIFIED: The application sees an internal http scheme.
VERIFIED: Canonicalization redirects http to https.
VERIFIED: The client already arrived over external https, producing a loop.

Concrete findings

The loop is caused by two views of scheme: external HTTPS and internal HTTP after TLS termination.
Canonicalization should trust forwarded scheme/host only from configured trusted proxies.
The /docs versus /docs/ case shows authentication returnTo and path canonicalization disagreeing; both must use one canonical path function.
Hop limits are a safety net, not the root fix; every redirect must move monotonically toward one destination.

The canonical acceptance rule is

Redirect logic is correct only when each redirect moves a request toward one canonical destination, proxy-derived scheme/host data is trusted according to deployment policy, and authentication/canonicalization rules cannot redirect each other indefinitely.

The current result is based on that invariant, not on a generic success banner or a reusable checklist.

Required actions

Canonical Host And Scheme: repair the owning boundary and preserve this case as a regression fixture; record the exa

About this skill

Repair HTTP Redirect Loops & Navigation Bugs is a ToolForge Labs workflow for HTTP redirect loops, canonical host/scheme logic, forwarded headers, path normalization, authentication redirects, hop limits, and browser/client tests. It performs the supplied case instead of returning a generic template, separates verified evidence from hypotheses, and produces bounded repair or readiness actions with deterministic validation.

Frequently Asked Questions

Repair HTTP Redirect Loops & Navigation Bugs