Qaynaq LABS · TOOLS

HTTP · 1xx Informational

103 Early Hints

Server sends preliminary response with headers before final response is ready.

When you see this status

  • Client requests resource with 'Prefer: respond-async' header
  • Server starts processing but needs time to generate full response
  • Server sends early hints to allow client to start preloading resources

Common causes

  • Long-running server-side processing
  • Resource-intensive computation
  • External API calls delaying response

How to debug it

  1. Verify client supports Early Hints (HTTP/1.1+)
  2. Check server logs for processing delays
  3. Inspect network traffic for 103 responses
  4. Ensure client handles 1xx responses correctly

Return this code in your framework

Express (Node.js)
app.get('/', (req, res) => {
  res.writeHead(103, { 'Link': '</style.css>; rel=preload; as=style' });
  res.writeHead(200);
  res.end('<html>...</html>');
});
FastAPI (Python)
from fastapi import FastAPI

app = FastAPI()

@app.get("/")
async def root():
    return {"message": "Hello World"}

@app.get("/early")
async def early_hints():
    return Response(
        content="",
        headers={"Link": "</style.css>; rel=preload; as=style"},
        status_code=103
    )
NestJS
import { Controller, Get, Res } from '@nestjs/common';
import { Response } from 'express';

@Controller()
export class AppController {
  @Get()
  getEarlyHints(@Res() res: Response) {
    res.writeHead(103, { 'Link': '</style.css>; rel=preload; as=style' });
    res.status(200).send('<html>...</html>');
  }
}
Go (net/http)
package main

import (
	"net/http"
)

func handler(w http.ResponseWriter, r *http.Request) {
	w.Header().Set("Link", "</style.css>; rel=preload; as=style")
	w.WriteHeader(103)
	w.WriteHeader(200)
	w.Write([]byte("<html>...</html>"))
}

func main() {
	http.HandleFunc("/", handler)
	http.ListenAndServe(":8080", nil)
}

About HTTP 103

HTTP status code 103 Early Hints is part of the 1xx Informational family. Server sends preliminary response with headers before final response is ready. Understanding it is essential for backend engineers, API designers, and anyone debugging integrations between services.

The Qaynaq Labs HTTP Status Code Explainer covers all standard codes with practical guidance: what triggers them, how to debug them in production, and exactly how to return them from common frameworks. Each code page is hand-curated and verified.

Frequently asked

Does every client support HTTP 103?

No. Clients must explicitly opt-in via 'Expect: 100-continue' or 'Prefer: respond-async' headers. Most browsers support it for resource preloading.

Can I send a body with a 103 response?

Technically yes, but it's discouraged. 103 responses should only include headers. The final response will contain the body.

Is 103 commonly used in production?

Rarely. It's primarily used for resource preloading in modern browsers. Most APIs don't implement it due to limited client support.