100 vs 102: Continue vs Processing
100 and 102 can look similar in logs, but they tell clients, crawlers, and API consumers different things.
| Aspect | 100 | 102 |
|---|---|---|
| Meaning | Continue describes how the server processed the request and what the client should do next. | Processing describes how the server processed the request and what the client should do next. |
| Typical use case | HTTP 100 Continue indicates a informational response outcome. | HTTP 102 Processing indicates a informational response outcome. |
| Caching/client behavior | Check cache headers and downstream behavior for 100. | Check cache headers and downstream behavior for 102. |
| SEO implications | Search crawlers interpret 100 according to informational semantics. | Search crawlers interpret 102 according to informational semantics. |
| API/backend impact | API clients may branch logic specifically on 100. | API clients may branch logic specifically on 102. |
When to use one vs the other
Use 100 when the response should communicate continue behavior; use 102 when processing is the accurate protocol signal.
A frequent mistake is swapping 100 and 102 for convenience; that causes client retry bugs, incorrect cache signals, and misleading monitoring data.
Decision summary: if user agents should receive the Continue signal, return 100; if they should receive Processing, return 102.
FAQ
What is the biggest difference between 100 and 102?
100 communicates Continue, while 102 communicates Processing. Choosing the right one keeps clients and intermediaries predictable.
Do 100 and 102 have SEO or caching impact?
Yes. Search engines and caches interpret status classes differently. Use each code according to its semantics to avoid accidental indexing, stale responses, or crawl inefficiency.
Can APIs safely return 100 instead of 102?
Only when it matches contract semantics. API clients often branch logic by exact code, so swapping them can break retries, auth handling, or user-facing errors.
Related guides: 100 Continue · 102 Processing