HTTP 302 Found: Meaning and Fix

302 Found

Meaning	The resource is temporarily at another URL.
When	A login redirect or a short-lived move.
Causes	Auth gates, POST-redirect-GET, and temporary campaigns.
Fix	Follow Location. If an API client is redirected to an HTML login page, it is calling a browser route.
Retry	Follow one redirect. A loop is the bug.
Alert?	Usually no. Alert only if an API that should return JSON starts redirecting.

Runs in your browser. Nothing you enter is stored.

Most 302s are not an incident

Alert only if an API that should return JSON starts redirecting.

curl -sS -X POST https://api.trigv.com/v1/events \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TRIGV_API_KEY" \
  -d '{"channel":"ops","title":"HTTP 302","level":"warning"}'

Get an API key All status codes

How to use it

Read what 302 means before changing a retry loop.
Check the common causes against the response body and the server log.
Follow the retry note. Retrying a 400 with the same body will fail again.
Alert only in the cases the verdict describes.

About this tool

HTTP 302 Found means The resource is temporarily at another URL. Servers send it when A login redirect or a short-lived move.

Common causes: Auth gates, POST-redirect-GET, and temporary campaigns. The practical fix is: Follow Location. If an API client is redirected to an HTML login page, it is calling a browser route.

Retry: Follow one redirect. A loop is the bug.

Alert on it? Usually no. Alert only if an API that should return JSON starts redirecting.

Trigv is a push for the moment a status starts mattering, not a log of every response. If the code is one you should hear about, the snippet posts a single event with level error or warning. The status page itself does not call your API.

Questions

What is HTTP 302?

The resource is temporarily at another URL.

Should the client retry?

Follow one redirect. A loop is the bug.

Should I alert on it?

Usually no. Alert only if an API that should return JSON starts redirecting.

How is this different from reading the spec?

The page adds a plain retry note and an alert verdict for people running the service, not only for people parsing the response.

301 Moved Permanently The resource has a new permanent URL. 304 Not Modified The cached copy is still valid. 307 Temporary Redirect The resource is temporarily elsewhere, and the method must stay the same. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.

HTTP 302 Found