2014
RFC 7034 - HTTP Header Field X-Frame-Options
by dzc
To improve the protection of web applications against clickjacking,
this document describes the X-Frame-Options HTTP header field, which
declares a policy, communicated from the server to the client
browser, regarding whether the browser may display the transmitted
content in frames that are part of other web pages.
2011
Serveur ? Une théière, svp !
by astrochoupe
Au contraire de la très fréquente Erreur 404 (« Document non trouvé »), l’Erreur 418 ne s’affichera jamais dans votre navigateur. Pourtant, elle existe officiellement et devrait retourner le message « Je suis une théière ».
2010
2009
Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
by Xavier Lacot & 1 other
Sure the most funny IETF RFC that I have been given to read. This document specifies a Hyper Text Coffee Pot Control Protocol (HTCPCP), based on HTTP, which permits the full request and responses necessary to control all devices capable of making the popular caffeinated hot beverages.
2008
RFC 2324 (rfc2324) - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
by benoit
RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
Blog Stéphane Bortzmeyer: Les normes du courrier électronique enfin entièrement internationalisées
by damdec & 1 other
Parmi les protocoles utilisés sur Internet, presque tous sont internationalisés depuis longtemps. Le dernier gros manque concernait les adresses de courrier électronique, obligées de s'en tenir à [email protected] alors qu'on voudrait pouvoir écrire à stéphane@internet-en-coopération.fr. Désormais, nous avons une solution, Internationalized Email, dont les normes sont désormais effectives.
HTTP/1.1 (DELETE, GET, HEAD, PUT, POST) : Alan Dean
by nhoizey & 10 others
An activity diagram to describe the resolution of HTTP response status codes, given various headers.
Enhancements to Internet email to Support Diverse Service Environments (lemonade) Charter
by cbrocas & 1 other (via)
2. Enhance the existing IMAP4 message retrieval and/or message
submission (RFC 2476) protocols to satisfy the requirements for
forwarding a message and/or its attachments without downloading
the message to the client and subsequently uploading the message to a
server.
XMPP Instant Messaging
by greut
As noted above, if a connected resource does not request the roster during a session, it SHOULD never receive presence subscriptions and the associated roster pushes.
finally know why my bot was an epic failure.
2007
The NTLM Authentication Protocol
by nhoizey
This article seeks to describe NTLM at an intermediate to advanced level of detail, suitable as a reference for implementors.
mnot’s Web log: 5005
by greut & 1 other (via)
Feed Paging and Archiving (nee Feed History) has finally made it to a standards-track RFC.
Who does need a web browser now?
http://www.ietf.org/rfc/rfc4646.txt
by nhoizey
This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object.
Tags for Identifying Languages
by Xavier Lacot
This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document, in combination with RFC 4647, replaces RFC 3066, which RFC 1766.
Writing I-Ds and RFCs using XML
by benoit
This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series.
