From 452b67cf148d3236a8c4a116f4850269b2373f6e Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Thu, 18 Jun 2026 13:18:53 +0000 Subject: [PATCH] Updates AGENTS.md to reflect usage of the tag that was added earlier this year. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1935474 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/AGENTS.md | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/docs/manual/AGENTS.md b/docs/manual/AGENTS.md index b8b6c0775a..9e6e9d4f7e 100644 --- a/docs/manual/AGENTS.md +++ b/docs/manual/AGENTS.md @@ -27,14 +27,33 @@ This is the documentation source for the [Apache HTTP Server](https://httpd.apac ## External Link Conventions +### `` — RFC References -Always link to the IETF Datatracker for RFC references: +Use the `` tag for all RFC references. The element content is the +RFC number (digits only). The rendered output is "RFC NNNN" linked to +the canonical URL. + +```xml +7230 +9110 +``` + +To link to a numbered section, use the `section` attribute: +```xml +2616 ``` -https://datatracker.ietf.org/doc/html/rfcNNNN + +To link to a named anchor (appendix, named heading, etc.), use `anchor`: +```xml +7231 +9110 ``` -For section-specific links, use fragment anchors: `#section-N.N` -Do NOT use `tools.ietf.org`, `www.rfc-editor.org`, `www.ietf.org/rfc/`, `www.w3.org/Protocols/`, `www.faqs.org/rfcs/`, or any other RFC mirror. These are legacy patterns — `datatracker.ietf.org` is the canonical standard for this documentation. +Do **not** use both `section` and `anchor` on the same element. + +Do **not** use `` with RFC URLs when the `` tag can +express the link. Use `` only for non-RFC resources, IETF drafts, or +cases where the display text must differ from "RFC NNNN". ## Directive Syntax Definitions -- 2.47.3