I cannot say if this is broadly accepted by HTTP clients, but speaking strictly RFC, the server should respond with:
HTTP/1.1 426 Upgrade Required
Upgrade: TLS/1.0, HTTP/1.1
Connection: Upgrade
More Related Contents:
- Max memory usage of a chrome process (tab) & how do I increase it?
- Correctly switching between HTTP and HTTPS using .htaccess
- HTTPS Proxy Server in node.js
- What is the difference between POST and PUT in HTTP?
- Is an entity body allowed for an HTTP DELETE request?
- REST HTTP status codes for failed validation or invalid duplicate
- URL matrix parameters vs. query parameters
- Is there any downside for using a leading double slash to inherit the protocol in a URL? i.e. src=”//domain.com”
- Easy HTTP requests with gzip/deflate compression
- Difference between Pragma and Cache-Control headers?
- Detecting the character encoding of an HTTP POST request
- Why does my web server software disallow PUT and DELETE requests?
- Content-Length header with HEAD requests?
- Which HTTP methods match up to which CRUD methods?
- HTTP status code for a partial successful request
- URL without “http|https”
- What is the difference between HTTP and REST?
- Doing a HTTP PUT from a browser
- REST response code for invalid data
- Are Callable Cloud Functions better than HTTP functions?
- Custom HTTP Authorization Header
- RESTful Alternatives to DELETE Request Body
- REST, HTTP DELETE and parameters
- HTTP and HTTPS iframe
- Can I stream a file upload to S3 without a content-length header?
- Page loaded over HTTPS but requested an insecure XMLHttpRequest endpoint
- Should I use PATCH or PUT in my REST API?
- How can I deal with HTTP GET query string length limitations and still want to be RESTful?
- Error “You’re accessing the development server over HTTPS, but it only supports HTTP”
- htaccess redirect for non-www both http and https