Matches in DBpedia 2016-04 for { ?s ?p "HTTP/1.1 introduced support for the Upgrade header field. In the exchange, the client begins by making a clear-text request, which is later upgraded to a newer http protocol version or switched to a different protocol. Connection upgrade must be requested by the client, if the server wants to enforce an upgrade it may send a \"426 upgrade required\" response. The client can then send a new request with the appropriate upgrade headers while keeping the connection open."@en }
Showing triples 1 to 2 of
2
with 100 triples per page.
- 1.1_Upgrade_header abstract "HTTP/1.1 introduced support for the Upgrade header field. In the exchange, the client begins by making a clear-text request, which is later upgraded to a newer http protocol version or switched to a different protocol. Connection upgrade must be requested by the client, if the server wants to enforce an upgrade it may send a \"426 upgrade required\" response. The client can then send a new request with the appropriate upgrade headers while keeping the connection open.".
- 1.1_Upgrade_header comment "HTTP/1.1 introduced support for the Upgrade header field. In the exchange, the client begins by making a clear-text request, which is later upgraded to a newer http protocol version or switched to a different protocol. Connection upgrade must be requested by the client, if the server wants to enforce an upgrade it may send a \"426 upgrade required\" response. The client can then send a new request with the appropriate upgrade headers while keeping the connection open.".