Free tools

HTTP 307 Temporary Redirect

The resource is temporarily elsewhere, and the method must stay the same. Free reference, no signup.

307 Temporary Redirect

MeaningThe resource is temporarily elsewhere, and the method must stay the same.
WhenA temporary move that should not turn a POST into a GET.
CausesMaintenance redirects and method-preserving proxies.
FixFollow Location with the original method and body.
RetryFollow the redirect once.
Alert?Usually no. Alert if an API client is bounced on every call.

Runs in your browser. Nothing you enter is stored.

Most 307s are not an incident

Alert if an API client is bounced on every call.

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 307","level":"warning"}'

How to use it

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

About this tool

HTTP 307 Temporary Redirect means The resource is temporarily elsewhere, and the method must stay the same. Servers send it when A temporary move that should not turn a POST into a GET.

Common causes: Maintenance redirects and method-preserving proxies. The practical fix is: Follow Location with the original method and body.

Retry: Follow the redirect once.

Alert on it? Usually no. Alert if an API client is bounced on every call.

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 307?

The resource is temporarily elsewhere, and the method must stay the same.

Should the client retry?

Follow the redirect once.

Should I alert on it?

Usually no. Alert if an API client is bounced on every call.

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.