What did 306 Switch Proxy mean?
It appeared only in a draft of HTTP/1.1 and was meant to tell clients to switch proxies. It was never standardised, and the number is now permanently reserved.
Reserved. Was "Switch Proxy" in a draft and is no longer used. 306 belongs to the 3xx redirection class and is defined in RFC 9110.
Loading the workbench.
Reserved. Was "Switch Proxy" in a draft and is no longer used. The code is registered with IANA and defined in RFC 9110.
Redirection: the client must take another step to finish the request. Every code from 300 to 399 shares that general meaning, so a client that does not recognise 306 must treat it like 300.
306 is reserved and unused. A draft of HTTP/1.1 briefly defined it as Switch Proxy, to tell clients to use a different proxy for subsequent requests, but the idea was dropped before standardisation. IANA keeps the number reserved so nobody gives it a new meaning that old software could misread. No legitimate server sends 306, and if you see one it almost certainly comes from a bug or a test harness.
Never send 306. A client that receives it should apply the generic 3xx rule, treating it as an unspecified redirection, and should not follow it automatically. If one of your services returns 306, check for a hand-coded status number or a typo in a redirect helper. Pick a real redirect such as 302, 307, or 308 depending on whether the move is temporary and whether the method must be preserved.
HTTP/1.1 306 (Unused)
(reserved: no server should send this status)306 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:
curl -i.Browse every code on the HTTP status codes page.
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.
It appeared only in a draft of HTTP/1.1 and was meant to tell clients to switch proxies. It was never standardised, and the number is now permanently reserved.
No. Reusing reserved codes confuses clients and proxies. Use a registered code that fits, or return a standard code with details in the body.
No. 306 is reserved and unused, so a correct server never sends it; a client that receives it should treat it like a generic 3xx response.
No. Caches store a 306 only when Cache-Control or Expires explicitly allows it.
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.
F12, or Cmd+Option+I on a Mac, and select the Network tab.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.