ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • HTTP service

302

HTTP 302 Found: the resource is temporarily at another URI

Verified with sources2 sourcesReviewed Aug 22, 2026
Technician coming? See what they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

HTTP 302 means the target resource is temporarily available at another URI, normally provided in the Location response field.

Safety first

Stop and check this first

  • Location URLs can contain one-time tokens or personal parameters. Redact them before sharing a redirect trace.

Safe checks you can perform

  • Record the redirect chain without secrets
  • Compare the method before and after 302
  • Check scheme, host and proxy rules

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Trace redirect ownership across every layer

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Trace redirect ownership across every layer

    What they doMap which edge, proxy or application emitted each Location field and remove the first contradictory rule.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Record the redirect chain without secrets

    Tools required

    Inspect each status and Location value, redacting tokens and query data, until the final response or repeated URI appears.

    Location URLs can contain one-time tokens or personal parameters. Redact them before sharing a redirect trace.

    Evidence: RFC 9110 section 15.4.3 - 302 Found · IANA Hypertext Transfer Protocol Status Code Registry

  2. Compare the method before and after 302

    Tools required

    Confirm whether the client changed POST to GET. Use 307 when the server requires method preservation.

    Location URLs can contain one-time tokens or personal parameters. Redact them before sharing a redirect trace.

    Evidence: RFC 9110 section 15.4.3 - 302 Found · IANA Hypertext Transfer Protocol Status Code Registry

  3. Check scheme, host and proxy rules

    No special tools

    Verify that HTTPS termination, canonical-host rules and application redirects agree and do not point back to one another.

    Location URLs can contain one-time tokens or personal parameters. Redact them before sharing a redirect trace.

    Evidence: RFC 9110 section 15.4.3 - 302 Found · IANA Hypertext Transfer Protocol Status Code Registry

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
HTTP
Product type
HTTP service

Known code variants

  • 302 Encontrado
  • 302 Found
  • 302 Gefunden
  • 302 Trouvé
  • 302 Trovato
  • código HTTP 302
  • error HTTP 302
  • événement Fronius 302
  • événement SMA 302
  • evento Fronius 302
  • evento SMA 302
  • Fronius Ereignis 302
  • Fronius event 302
  • Fronius inverter 302
  • Fronius Symo / Eco 302
  • Fronius Wechselrichter 302
  • Growatt 302 sin conexión de red
  • Growatt error 302
  • Growatt Error: 302
  • Growatt No AC Connection
  • Growatt no grid connection
  • HTTP 302
  • HTTP error 302
  • HTTP status 302
  • inversor Fronius 302
  • inversor SMA 302
  • inverter Fronius 302
  • inverter SMA 302
  • onduleur Fronius 302
  • onduleur SMA 302
  • SMA Ereignis 302
  • SMA event 302
  • SMA inverter 302
  • SMA Wechselrichter 302
  • status code 302
  • Sunny Tripower X 302

What it means

The client should continue using the original URI for future requests. Historical behavior allows some user agents to change POST to GET while following 302.

Warnings and stop conditions

  • Higheditorial warning

    Location URLs can contain one-time tokens or personal parameters. Redact them before sharing a redirect trace.

    Evidence: RFC 9110 section 15.4.3 - 302 Found · IANA Hypertext Transfer Protocol Status Code Registry

Symptoms and causes

Probable causes · in order

  • The service intentionally uses a temporary redirectConfirmed

    Authentication, regional routing and temporary migrations can direct the current request to a different URI.

    Evidence: RFC 9110 section 15.4.3 - 302 Found · IANA Hypertext Transfer Protocol Status Code Registry

  • A redirect loop or method change broke the flowPossible

    Misaligned proxy and application rules can bounce requests or turn a redirected POST into GET.

    Evidence: RFC 9110 section 15.4.3 - 302 Found · IANA Hypertext Transfer Protocol Status Code Registry

Virtual technician

Does 302 still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    RFC 9110 section 15.4.3 - 302 Found

    Internet Engineering Task Force · 2022 · official_doc

  2. 2

    IANA Hypertext Transfer Protocol Status Code Registry

    Internet Assigned Numbers Authority · 2025 · official_doc

Sources: RFC 9110 section 15.4.3 - 302 Found · IANA Hypertext Transfer Protocol Status Code Registryreviewed 2026-08-22 · verified

Was this entry useful?