From daaf8cba41f91dd9421f8b4daf376b9d15d8ca0f Mon Sep 17 00:00:00 2001 From: Andres Rey Date: Fri, 23 Dec 2016 13:51:24 -0300 Subject: Corrected even more test cases --- test/test-pages/ietf-1/expected.html | 38 ++++++++++++++++++------------------ 1 file changed, 19 insertions(+), 19 deletions(-) (limited to 'test/test-pages/ietf-1') diff --git a/test/test-pages/ietf-1/expected.html b/test/test-pages/ietf-1/expected.html index 8d80a2e..eab8ec5 100644 --- a/test/test-pages/ietf-1/expected.html +++ b/test/test-pages/ietf-1/expected.html @@ -1,7 +1,7 @@
-[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]



Versions: 00 01 02 03 04



INTERNET DRAFT                                      Michiel B. de Jong
-Document: draft-dejong-remotestorage-04                   IndieHosters
+[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]               

Versions: 00 01 02 03 04

INTERNET DRAFT                                      Michiel B. de Jong
+Document: draft-dejong-remotestorage-04                   IndieHosters
                                                              F. Kooman
 Intended Status: Proposed Standard                       (independent)
 Expires: 18 June 2015                                 15 December 2014
@@ -22,7 +22,7 @@ Abstract
 Status of this Memo
 
    This Internet-Draft is submitted in full conformance with the
-   provisions of BCP 78 and BCP 79.
+   provisions of BCP 78 and BCP 79.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
@@ -41,7 +41,7 @@ Copyright Notice
    Copyright (c) 2014 IETF Trust and the persons identified as the
    document authors. All rights reserved.
 
-   This document is subject to BCP 78 and the IETF Trust's Legal
+   This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -126,7 +126,7 @@ Table of Contents
 
     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
-    document are to be interpreted as described in RFC 2119 [WORDS].
+    document are to be interpreted as described in RFC 2119 [WORDS].
 
     "SHOULD" and "SHOULD NOT" are appropriate when valid exceptions to a
     general requirement are known to exist or appear to exist, and it is
@@ -395,7 +395,7 @@ Table of Contents
          can however be reused in subsequent interactions with the same
          client, as long as that client is still trusted. Example:
          * 'ofb24f1ac3973e70j6vts19qr9v2eei'
-       * <storage_api>, always 'draft-dejong-remotestorage-04' for this
+       * <storage_api>, always 'draft-dejong-remotestorage-04' for this
          alternative version of the specification.
 
     The client can make its requests using https with CORS and bearer
@@ -632,7 +632,7 @@ g.com HTTP/1.1
              "href": "https://3pp.io:4439/storage/michiel",
              "rel": "remotestorage",
              "properties": {
-               "http://remotestorage.io/spec/version": "draft-dejong-re\
+               "http://remotestorage.io/spec/version": "draft-dejong-re\
 motestorage-04",
                "http://tools.ietf.org/html/rfc6749#section-4.2": "https\
 ://3pp.io:4439/oauth/michiel",
@@ -999,7 +999,7 @@ charset=UTF-8","Content-Length":106}}}
 
     [WORDS]
         Bradner, S., "Key words for use in RFCs to Indicate Requirement
-        Levels", BCP 14, RFC 2119, March 1997.
+        Levels", BCP 14, RFC 2119, March 1997.
 
 
 de Jong                                                        [Page 20]
@@ -1010,32 +1010,32 @@ charset=UTF-8","Content-Length":106}}}
 
     [IRI]
         Duerst, M., "Internationalized Resource Identifiers (IRIs)",
-        RFC 3987, January 2005.
+        RFC 3987, January 2005.
 
     [WEBFINGER]
         Jones, P., Salguerio, G., Jones, M, and Smarr, J.,
-        "WebFinger", RFC7033, September 2013.
+        "WebFinger", RFC7033, September 2013.
 
     [OAUTH]
         "Section 4.2: Implicit Grant", in: Hardt, D. (ed), "The OAuth
-        2.0 Authorization Framework", RFC6749, October 2012.
+        2.0 Authorization Framework", RFC6749, October 2012.
 
 17.2. Informative References
 
     [HTTPS]
-        Rescorla, E., "HTTP Over TLS", RFC2818, May 2000.
+        Rescorla, E., "HTTP Over TLS", RFC2818, May 2000.
 
     [HTTP]
         Fielding et al., "Hypertext Transfer Protocol (HTTP/1.1):
-        Semantics and Content", RFC7231, June 2014.
+        Semantics and Content", RFC7231, June 2014.
 
     [COND]
         Fielding et al., "Hypertext Transfer Protocol (HTTP/1.1):
-        Conditional Requests", RFC7232, June 2014.
+        Conditional Requests", RFC7232, June 2014.
 
     [RANGE]
         Fielding et al., "Hypertext Transfer Protocol (HTTP/1.1):
-        Conditional Requests", RFC7233, June 2014.
+        Conditional Requests", RFC7233, June 2014.
 
     [SPDY]
         Mark Belshe, Roberto Peon, "SPDY Protocol - Draft 3.1", http://
@@ -1070,11 +1070,11 @@ charset=UTF-8","Content-Length":106}}}
 
     [KERBEROS]
         C. Neuman et al., "The Kerberos Network Authentication Service
-        (V5)", RFC4120, July 2005.
+        (V5)", RFC4120, July 2005.
 
     [BEARER]
         M. Jones, D. Hardt, "The OAuth 2.0 Authorization Framework:
-        Bearer Token Usage", RFC6750, October 2012.
+        Bearer Token Usage", RFC6750, October 2012.
 
     []
         "Using remoteStorage for web authoring", reSite wiki, retrieved
@@ -1104,7 +1104,7 @@ charset=UTF-8","Content-Length":106}}}
 
 de Jong                                                        [Page 22]
 
-


Html markup produced by rfcmarkup 1.111, available from +
Html markup produced by rfcmarkup 1.111, available from https://tools.ietf.org/tools/rfcmarkup/ -
\ No newline at end of file +

\ No newline at end of file -- cgit v1.2.3