Introduction For 32 years now, the venerable HTTP protocol has been at the heart of the Web. This protocol enables “resources” (anything that can be named can be a resource, but these are often documents) to be retrieved from a server using their unique identifier: their URL. Since 1991, the Web has exploded in popularity,…
Tag: RFC
Using the “103 Early Hints” Status Code in Go Applications
103 is a new experimental HTTP status code defined in RFC 8297. It’s an informational status that can be sent by a server before the main HTTP response. Used in conjunction with the Link HTTP header and the preload relation, 103 gives the client the opportunity to fetch resources (assets, images, linked API documents…) related…
Internationalized Domain Name (IDN) and PHP
Currently, PHP doesn’t have any native support of IDN: domains with non-ASCII characters such as http://www.académie-française.fr. If you try to connect to such site you’ll get nothing but an error: file_get_contents(‘http://académie-française.fr’); // PHP Warning: file_get_contents(): php_network_getaddresses: getaddrinfo failed: nodename nor servname provided, or not known in php shell code on line 1 RFC 3490 specifies that applications must convert IDN…