HTTP 500 INTERNAL SERVER ERROR

A generic server failure, usually an unhandled exception. 500 belongs to the 5xx server error class and is defined in RFC 9110.

Loading the workbench.

About HTTP 500

What Does HTTP 500 Internal Server Error Mean?

A generic server failure, usually an unhandled exception. The code is registered with IANA and defined in RFC 9110.

Server error: the server failed to fulfill a valid request. Every code from 500 to 599 shares that general meaning, so a client that does not recognise 500 must treat it like 500.

When Do You See a 500 Response?

500 Internal Server Error is the generic failure an application returns when something went wrong that it did not anticipate: an unhandled exception, a null reference, a failed database query, a misconfigured environment variable, or a broken deploy. Frameworks and web servers send it when code crashes before producing a response. The status itself says nothing specific; the useful detail lives in the server logs, not in the response.

How Do You Fix a 500?

Users can retry later, but a persistent 500 needs a developer. Check the application and server error logs around the time of the request, using a request ID header if the service provides one. Servers should never expose stack traces or secrets in the body on production. Where the cause is known, use a more specific code, such as 502, 503, or 504, so clients and monitoring can react appropriately.

What Does a 500 Response Look Like?

HTTP/1.1 500 Internal Server Error
Content-Type: application/problem+json
X-Request-Id: 9c1f27a4

500 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.

To inspect a real one without sending it anywhere:

Copy the response headers from your browser Network tab, or from curl -i.
Paste them into the Header decoder to see every header explained.
Check caching in the Cache lane.

Which Status Codes Are Related to 500?

502 Bad Gateway: A proxy or gateway got an invalid response from the upstream server.
503 Service Unavailable: Overloaded or down for maintenance. Retry-After may say when it will return.
504 Gateway Timeout: A proxy or gateway gave up waiting for the upstream server.
501 Not Implemented: The server does not support the method at all.

Browse every code on the HTTP status codes page.

What Other Lanes Are in the Reference Section?

HTTP status codes: Every IANA-registered status code, with a page per code.
MIME types: File extensions to Content-Type, searchable both ways, plus a Content-Type parser.
HTTP methods: GET, POST, PUT, PATCH, DELETE and the rest: safe, idempotent, cacheable.

Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.

Frequently Asked Questions

Is a 500 error my fault as a visitor?

Almost never. It means the server failed while handling a request it should have been able to process. Retrying later or reporting it to the site owner is all you can do.

Should a 500 response show the error details?

Not in production. Stack traces and messages can leak paths, queries, and secrets. Log the details server-side and return a short message with a request ID.

Is HTTP 500 an error?

Yes. 500 is a server error response: the server failed to handle a valid request, so retrying later may work.

Is a 500 response cacheable by default?

No. Caches store a 500 only when Cache-Control or Expires explicitly allows it.

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.

Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your headers.
Click the clear icon in the Network tab so that the log is empty.
Paste real headers into any lane and read the result.
Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and every lane keeps working.

Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.

2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.

Was this helpful?