Changeset 90

Timestamp:

21/12/07 23:39:44 (14 years ago)

Author:

fielding@…

Message:

Resolve #42: RFC2606 compliance

Use example.org, example.com, and example.net instead
of real domains in examples.

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.xml (modified) (5 diffs)
• p2-semantics.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1055 +1055 @@
 </t>
 <figure><artwork type="example">
-   http://abc.com:80/~smith/home.html
-   http://ABC.com/%7Esmith/home.html
-   http://ABC.com:/%7esmith/home.html
+   http://example.com:80/~smith/home.html
+   http://EXAMPLE.com/%7Esmith/home.html
+   http://EXAMPLE.com:/%7esmith/home.html
 </artwork></figure>
 </section>
@@ -1598 +1598 @@
 </t>
 <figure><artwork type="example">
-    GET http://www.w3.org/pub/WWW/TheProject.html HTTP/1.1
+    GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
 </artwork></figure>
 <t>
@@ -1616 +1616 @@
    be transmitted in a Host header field. For example, a client wishing
    to retrieve the resource above directly from the origin server would
-   create a TCP connection to port 80 of the host "www.w3.org" and send
+   create a TCP connection to port 80 of the host "www.example.org" and send
    the lines:
 </t>
 <figure><artwork type="example">
     GET /pub/WWW/TheProject.html HTTP/1.1
-    Host: www.w3.org
+    Host: www.example.org
 </artwork></figure>
 <t>
@@ -2361 +2361 @@
    port for the service requested (e.g., "80" for an HTTP URL). For
    example, a request on the origin server for
-   &lt;http://www.w3.org/pub/WWW/&gt; would properly include:
+   &lt;http://www.example.org/pub/WWW/&gt; would properly include:
 </t>
 <figure><artwork type="example">
     GET /pub/WWW/ HTTP/1.1
-    Host: www.w3.org
+    Host: www.example.org
 </artwork></figure>
 <t>
@@ -2638 +2638 @@
    For example, a request message could be sent from an HTTP/1.0 user
    agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
-   forward the request to a public proxy at nowhere.com, which completes
-   the request by forwarding it to the origin server at www.ics.uci.edu.
-   The request received by www.ics.uci.edu would then have the following
+   forward the request to a public proxy at p.example.net, which completes
+   the request by forwarding it to the origin server at www.example.com.
+   The request received by www.example.com would then have the following
    Via header field:
 </t>
 <figure><artwork type="example">
-    Via: 1.0 fred, 1.1 nowhere.com (Apache/1.1)
+    Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
 </artwork></figure>
 <t>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1719 +1719 @@
 </t>
 <figure><artwork type="example">
-    From: webmaster@w3.org
+    From: webmaster@example.org
 </artwork></figure>
 <t>
@@ -1765 +1765 @@
 </t>
 <figure><artwork type="example">
-    Location: http://www.w3.org/pub/WWW/People.html
+    Location: http://www.example.org/pub/WWW/People.html
 </artwork></figure>
 <t>
@@ -1833 +1833 @@
 </t>
 <figure><artwork type="example">
-    Referer: http://www.w3.org/hypertext/DataSources/Overview.html
+    Referer: http://www.example.org/hypertext/Overview.html
 </artwork></figure>
 <t>