Why does REST test test require an HTML5-capable browser?

Updated

REST test test (resttesttest.com) requires an HTML5-capable browser because its core action — the Ajax Request button — sends HTTP requests from the page itself using browser APIs that only exist in HTML5-era browsers. If you open the tool in an older browser, the page may load, but the request feature won't work. To use it, open the site in a current version of Chrome, Firefox, Edge, or Safari.

What the page actually says

The tool's own note is short and direct:

"Use this simple page to poke around at the API. Specify HTTP method, URL and parameters, and click on Ajax Request. Note that this page requires a browser with HTML5 support."

Two things follow from that sentence:

  • The requirement is tied to the Ajax request feature, not to viewing the page.
  • "HTML5 support" is the page's shorthand for the browser capabilities that feature depends on.

Why HTML5 matters for this specific tool

REST test test is a client-side page. It doesn't send your request from a server on its behalf — the browser does the work. That means it relies on modern browser features that older browsers either lack or implement inconsistently:

Capability Why the tool needs it
XMLHttpRequest Level 2 / fetch-style behavior Sending GET, POST, PUT, DELETE, HEAD, and OPTIONS requests from the page
Cross-origin request handling (CORS) Calling APIs on other domains and reading the response
FormData / file handling The Add file option for multipart requests
Modern DOM and event APIs Reading your inputs and updating the response area without a page reload

Older browsers (for example, Internet Explorer 8 and earlier) predate or only partially implement these. In those browsers, clicking Ajax Request typically does nothing, throws a script error, or fails silently — which is exactly the confusing behavior that sends people looking for an explanation.

How to tell whether your browser is the problem

  1. Open resttesttest.com.
  2. Enter a simple public endpoint, choose GET, and click Ajax Request.
  3. If you get a response (status code, headers, or body), your browser is fine — the issue is elsewhere.
  4. If nothing happens, check your browser version. If it's more than a few years old, or an obsolete browser like IE, that's the likely cause.

If the page loads but the button appears dead, browser capability is the first thing to rule out, before you suspect the API or your network.

Common points of confusion

  • "The page loaded, so it should work." Loading HTML and running the request feature are different requirements. An old browser can render the form and still fail at the Ajax step.
  • "It's a network or CORS error." If you see a CORS or network message in the console, the request did attempt to run — that points to the target API's headers, not your browser version.
  • "Any modern browser is fine." Generally yes, but keep the browser updated. Very old versions of otherwise modern browsers can still miss pieces of the API surface the tool uses.

What to do

  • Use a current, updated browser. Chrome, Firefox, Edge, and Safari in recent versions all satisfy the requirement.
  • If you're stuck on an old browser or a locked-down environment, the tool isn't the right fit — you'd need a different client, such as a command-line tool or a desktop API client, that doesn't depend on in-browser HTML5 APIs.
  • If a modern browser still fails, the cause is almost certainly the request itself (URL, method, headers, or the target API's CORS policy), not HTML5 support.