STATIC DELIVERY LAB

Static files.
Real responses.

Explore how a static site is served over HTTPS. Inspect the headers this server sends, test cache validation, and take a minimal Nginx setup with you.

terminal — health check
# Run against this origin
$ curl -i https://portal.neon-static.com/healthz

HTTP/2 200
content-type: text/plain
cache-control: no-cache

ok
Example response Check live ↓

THE BASICS

What a static server does

HTTPS delivery

Serve HTML, styles and other assets with TLS. This origin supports HTTP/2.

Read about HTTPS →

Content types

See how the same server identifies HTML, CSS and JSON so clients can handle each file correctly.

Compare responses →

Health checks

A plain-text endpoint answers with ok when the web server can handle the request.

Open health endpoint →

LIVE REQUEST

Response inspector

Choose a file on this site. The inspector makes a real request from your browser and shows its status, timing and response headers.

Ready to send

Response headers will appear here.

QUICKSTART

Serve your first folder

Use the sample Nginx configuration and verify it with curl.

Open quickstart →