diff options
Diffstat (limited to 'plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/ietf-1/expected.html')
| -rw-r--r-- | plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/ietf-1/expected.html | 139 |
1 files changed, 72 insertions, 67 deletions
diff --git a/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/ietf-1/expected.html b/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/ietf-1/expected.html index ff46f7a1d..ab794ec4d 100644 --- a/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/ietf-1/expected.html +++ b/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/ietf-1/expected.html @@ -1,6 +1,10 @@ <div> -<span>[<a href="http://fakehost/test/../html/" title="Document search and retrieval page">Docs</a>] [<a href="https://tools.ietf.org/id/draft-dejong-remotestorage-04.txt" title="Plaintext version of this document">txt</a>|<a href="http://fakehost/pdf/draft-dejong-remotestorage-04.txt" title="PDF version of this document">pdf</a>] [<a href="https://datatracker.ietf.org/doc/draft-dejong-remotestorage" title="IESG Datatracker information for this document">Tracker</a>] [<a href="mailto:[email protected]?subject=draft-dejong-remotestorage%20" title="Send email to the document authors">Email</a>] [<a href="http://fakehost/rfcdiff?difftype=--hwdiff&url2=draft-dejong-remotestorage-04.txt" title="Inline diff (wdiff)">Diff1</a>] [<a href="http://fakehost/rfcdiff?url2=draft-dejong-remotestorage-04.txt" title="Side-by-side diff">Diff2</a>] [<a href="http://fakehost/idnits?url=https://tools.ietf.org/id/draft-dejong-remotestorage-04.txt" title="Run an idnits check of this document">Nits</a>] </span><br></br><span> </span><br></br><span>Versions: <a href="http://fakehost/test/draft-dejong-remotestorage-00">00</a> <a href="http://fakehost/test/draft-dejong-remotestorage-01">01</a> <a href="http://fakehost/test/draft-dejong-remotestorage-02">02</a> <a href="http://fakehost/test/draft-dejong-remotestorage-03">03</a> <a href="http://fakehost/test/draft-dejong-remotestorage-04">04</a> </span><br></br><span> </span><br></br><pre>INTERNET DRAFT Michiel B. de Jong +<span>[<a href="http://fakehost/html/" title="Document search and retrieval page">Docs</a>] [<a href="https://tools.ietf.org/id/draft-dejong-remotestorage-04.txt" title="Plaintext version of this document">txt</a>|<a href="http://fakehost/pdf/draft-dejong-remotestorage-04.txt" title="PDF version of this document">pdf</a>] [<a href="https://datatracker.ietf.org/doc/draft-dejong-remotestorage" title="IESG Datatracker information for this document">Tracker</a>] [<a href="mailto:[email protected]?subject=draft-dejong-remotestorage%20" title="Send email to the document authors">Email</a>] [<a href="http://fakehost/rfcdiff?difftype=--hwdiff&url2=draft-dejong-remotestorage-04.txt" title="Inline diff (wdiff)">Diff1</a>] [<a href="http://fakehost/rfcdiff?url2=draft-dejong-remotestorage-04.txt" title="Side-by-side diff">Diff2</a>] [<a href="http://fakehost/idnits?url=https://tools.ietf.org/id/draft-dejong-remotestorage-04.txt" title="Run an idnits check of this document">Nits</a>] </span><br> +<span> </span><br> +<span>Versions: <a href="http://fakehost/test/draft-dejong-remotestorage-00">00</a> <a href="http://fakehost/test/draft-dejong-remotestorage-01">01</a> <a href="http://fakehost/test/draft-dejong-remotestorage-02">02</a> <a href="http://fakehost/test/draft-dejong-remotestorage-03">03</a> <a href="http://fakehost/test/draft-dejong-remotestorage-04">04</a> </span><br> +<span> </span><br> +<pre>INTERNET DRAFT Michiel B. de Jong Document: <a href="http://fakehost/test/draft-dejong-remotestorage-04">draft-dejong-remotestorage-04</a> IndieHosters F. Kooman Intended Status: Proposed Standard (independent) @@ -53,7 +57,7 @@ Copyright Notice <span>de Jong [Page 1]</span> -</pre><pre><a href="#page-2" id="page-2" name="page-2"> </a> +</pre><pre><a name="page-2" id="page-2" href="#page-2"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -89,7 +93,7 @@ Table of Contents <a href="#section-18">18</a>. Authors' addresses............................................<a href="#page-22">22</a> -<span><a href="#section-1" name="section-1">1</a>. Introduction</span> +<span><a name="section-1" href="#section-1">1</a>. Introduction</span> Many services for data storage are available over the internet. This specification describes a vendor-independent interface for such @@ -103,7 +107,7 @@ Table of Contents <span>de Jong [Page 2]</span> -</pre><pre><a href="#page-3" id="page-3" name="page-3"> </a> +</pre><pre><a name="page-3" id="page-3" href="#page-3"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -122,7 +126,7 @@ Table of Contents The exact details of these four actions are described in this specification. -<span><a href="#section-2" name="section-2">2</a>. Terminology</span> +<span><a name="section-2" href="#section-2">2</a>. Terminology</span> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this @@ -135,7 +139,7 @@ Table of Contents implement the general requirement when such failure would result in interoperability failure. -<span><a href="#section-3" name="section-3">3</a>. Storage model</span> +<span><a name="section-3" href="#section-3">3</a>. Storage model</span> The server stores data in nodes that form a tree structure. Internal nodes are called 'folders' and leaf nodes are called @@ -153,7 +157,7 @@ Table of Contents <span>de Jong [Page 3]</span> -</pre><pre><a href="#page-4" id="page-4" name="page-4"> </a> +</pre><pre><a name="page-4" id="page-4" href="#page-4"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -163,7 +167,7 @@ Table of Contents * content length * content -<span><a href="#section-4" name="section-4">4</a>. Requests</span> +<span><a name="section-4" href="#section-4">4</a>. Requests</span> Client-to-server requests SHOULD be made over https [<a href="#ref-HTTPS">HTTPS</a>], and servers MUST comply with HTTP/1.1 [<a href="#ref-HTTP">HTTP</a>]. Specifically, they @@ -203,7 +207,7 @@ Table of Contents <span>de Jong [Page 4]</span> -</pre><pre><a href="#page-5" id="page-5" name="page-5"> </a> +</pre><pre><a name="page-5" id="page-5" href="#page-5"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -253,7 +257,7 @@ Table of Contents <span>de Jong [Page 5]</span> -</pre><pre><a href="#page-6" id="page-6" name="page-6"> </a> +</pre><pre><a name="page-6" id="page-6" href="#page-6"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -303,11 +307,11 @@ Table of Contents <span>de Jong [Page 6]</span> -</pre><pre><a href="#page-7" id="page-7" name="page-7"> </a> +</pre><pre><a name="page-7" id="page-7" href="#page-7"> </a> <span>Internet-Draft remoteStorage December 2014</span> -<span><a href="#section-5" name="section-5">5</a>. Response codes</span> +<span><a name="section-5" href="#section-5">5</a>. Response codes</span> Response codes SHOULD be given as defined by [HTTP, <a href="#section-6">section 6</a>] and [BEARER, <a href="#section-3.1">section 3.1</a>]. The following is a non-normative checklist @@ -340,7 +344,7 @@ Table of Contents Clients SHOULD also handle the case where a response takes too long to arrive, or where no response is received at all. -<span><a href="#section-6" name="section-6">6</a>. Versioning</span> +<span><a name="section-6" href="#section-6">6</a>. Versioning</span> All successful requests MUST return an 'ETag' header [<a href="#ref-HTTP">HTTP</a>] with, in the case of GET, the current version, in the case of PUT, the new @@ -353,7 +357,7 @@ Table of Contents <span>de Jong [Page 7]</span> -</pre><pre><a href="#page-8" id="page-8" name="page-8"> </a> +</pre><pre><a name="page-8" id="page-8" href="#page-8"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -370,14 +374,14 @@ Table of Contents A provider MAY offer version rollback functionality to its users, but this specification does not define the user interface for that. -<span><a href="#section-7" name="section-7">7</a>. CORS headers</span> +<span><a name="section-7" href="#section-7">7</a>. CORS headers</span> All responses MUST carry CORS headers [<a href="#ref-CORS">CORS</a>]. The server MUST also reply to OPTIONS requests as per CORS. For GET requests, a wildcard origin MAY be returned, but for PUT and DELETE requests, the response MUST echo back the Origin header sent by the client. -<span><a href="#section-8" name="section-8">8</a>. Session description</span> +<span><a name="section-8" href="#section-8">8</a>. Session description</span> The information that a client needs to receive in order to be able to connect to a server SHOULD reach the client as described in the @@ -403,7 +407,7 @@ Table of Contents <span>de Jong [Page 8]</span> -</pre><pre><a href="#page-9" id="page-9" name="page-9"> </a> +</pre><pre><a name="page-9" id="page-9" href="#page-9"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -418,7 +422,7 @@ Table of Contents * https://storage.example.com/bob/public/documents/ * https://storage.example.com/bob/public/documents/draft.txt -<span><a href="#section-9" name="section-9">9</a>. Bearer tokens and access control</span> +<span><a name="section-9" href="#section-9">9</a>. Bearer tokens and access control</span> A bearer token represents one or more access scopes. These access scopes are represented as strings of the form <module> <level>, @@ -453,12 +457,12 @@ Table of Contents <span>de Jong [Page 9]</span> -</pre><pre><a href="#page-10" id="page-10" name="page-10"> </a> +</pre><pre><a name="page-10" id="page-10" href="#page-10"> </a> <span>Internet-Draft remoteStorage December 2014</span> -<span><a href="#section-10" name="section-10">10</a>. Application-first bearer token issuance</span> +<span><a name="section-10" href="#section-10">10</a>. Application-first bearer token issuance</span> To make a remoteStorage server available as 'the remoteStorage of <account> at <host>', exactly one link of the following format @@ -503,7 +507,7 @@ Table of Contents <span>de Jong [Page 10]</span> -</pre><pre><a href="#page-11" id="page-11" name="page-11"> </a> +</pre><pre><a name="page-11" id="page-11" href="#page-11"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -533,7 +537,7 @@ Table of Contents client_id parameter in favor of relying on the redirect_uri parameter for client identification. -<span><a href="#section-11" name="section-11">11</a>. Storage-first bearer token issuance</span> +<span><a name="section-11" href="#section-11">11</a>. Storage-first bearer token issuance</span> The provider MAY also present a dashboard to the user, where they have some way to add open web app manifests [<a href="#ref-MANIFEST">MANIFEST</a>]. Adding a @@ -553,7 +557,7 @@ Table of Contents <span>de Jong [Page 11]</span> -</pre><pre><a href="#page-12" id="page-12" name="page-12"> </a> +</pre><pre><a name="page-12" id="page-12" href="#page-12"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -591,19 +595,19 @@ Table of Contents debug tool, thus bypassing the need for an OAuth dance. Clients SHOULD NOT rely on this in production. -<span><a href="#section-12" name="section-12">12</a>. Example wire transcripts</span> +<span><a name="section-12" href="#section-12">12</a>. Example wire transcripts</span> The following examples are not normative ("\" indicates a line was wrapped). -<span><a href="#section-12.1" name="section-12.1">12.1</a>. WebFinger</span> +<span><a name="section-12.1" href="#section-12.1">12.1</a>. WebFinger</span> In application-first, an in-browser application might issue the following request, using XMLHttpRequest and CORS: <span>de Jong [Page 12]</span> -</pre><pre><a href="#page-13" id="page-13" name="page-13"> </a> +</pre><pre><a name="page-13" id="page-13" href="#page-13"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -643,7 +647,7 @@ motestorage-04", }] } -<span><a href="#section-12.2" name="section-12.2">12.2</a>. OAuth dialog form</span> +<span><a name="section-12.2" href="#section-12.2">12.2</a>. OAuth dialog form</span> Once the in-browser application has discovered the server's OAuth end-point, it will typically redirect the user to this URL, in @@ -653,7 +657,7 @@ motestorage-04", <span>de Jong [Page 13]</span> -</pre><pre><a href="#page-14" id="page-14" name="page-14"> </a> +</pre><pre><a name="page-14" id="page-14" href="#page-14"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -673,7 +677,7 @@ unhosted.5apps.com&response_type=token HTTP/1.1 <title>Allow access?</title> ... -<span><a href="#section-12.3" name="section-12.3">12.3</a>. OAuth dialog form submission</span> +<span><a name="section-12.3" href="#section-12.3">12.3</a>. OAuth dialog form submission</span> When the user submits the form, the request would look something like this: @@ -698,12 +702,12 @@ low Location:https://drinks-unhosted.5apps.com/#access_token=j2YnGt\ XjzzzHNjkd1CJxoQubA1o%3D&token_type=bearer&state= -<span><a href="#section-12.4" name="section-12.4">12.4</a>. OPTIONS preflight</span> +<span><a name="section-12.4" href="#section-12.4">12.4</a>. OPTIONS preflight</span> <span>de Jong [Page 14]</span> -</pre><pre><a href="#page-15" id="page-15" name="page-15"> </a> +</pre><pre><a name="page-15" id="page-15" href="#page-15"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -726,7 +730,7 @@ XjzzzHNjkd1CJxoQubA1o%3D&token_type=bearer&state= Access-Control-Allow-Headers: Authorization, Content-Length, Co\ ntent-Type, Origin, X-Requested-With, If-Match, If-None-Match -<span><a href="#section-12.5" name="section-12.5">12.5</a>. Initial PUT</span> +<span><a name="section-12.5" href="#section-12.5">12.5</a>. Initial PUT</span> An initial PUT may contain an 'If-None-Match: *' header, like this: @@ -749,11 +753,11 @@ ntent-Type, Origin, X-Requested-With, If-Match, If-None-Match Access-Control-Allow-Origin: <a href="https://drinks-unhosted.5apps.com">https://drinks-unhosted.5apps.com</a> ETag: "1382694045000" -<span><a href="#section-12.6" name="section-12.6">12.6</a>. Subsequent PUT</span> +<span><a name="section-12.6" href="#section-12.6">12.6</a>. Subsequent PUT</span> <span>de Jong [Page 15]</span> -</pre><pre><a href="#page-16" id="page-16" name="page-16"> </a> +</pre><pre><a name="page-16" id="page-16" href="#page-16"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -779,7 +783,7 @@ e.io/spec/modules/myfavoritedrinks/drink"} Access-Control-Allow-Origin: <a href="https://drinks-unhosted.5apps.com">https://drinks-unhosted.5apps.com</a> ETag: "1382694048000" -<span><a href="#section-12.7" name="section-12.7">12.7</a>. GET</span> +<span><a name="section-12.7" href="#section-12.7">12.7</a>. GET</span> A GET request would also include the bearer token, and optionally an If-None-Match header: @@ -803,7 +807,7 @@ e.io/spec/modules/myfavoritedrinks/drink"} <span>de Jong [Page 16]</span> -</pre><pre><a href="#page-17" id="page-17" name="page-17"> </a> +</pre><pre><a name="page-17" id="page-17" href="#page-17"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -838,7 +842,7 @@ charset=UTF-8","Content-Length":106}}} HTTP/1.1 404 Not Found Access-Control-Allow-Origin: <a href="https://drinks-unhosted.5apps.com">https://drinks-unhosted.5apps.com</a> -<span><a href="#section-12.8" name="section-12.8">12.8</a>. DELETE</span> +<span><a name="section-12.8" href="#section-12.8">12.8</a>. DELETE</span> A DELETE request may look like this: @@ -853,7 +857,7 @@ charset=UTF-8","Content-Length":106}}} <span>de Jong [Page 17]</span> -</pre><pre><a href="#page-18" id="page-18" name="page-18"> </a> +</pre><pre><a name="page-18" id="page-18" href="#page-18"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -863,7 +867,7 @@ charset=UTF-8","Content-Length":106}}} Access-Control-Allow-Origin: <a href="https://drinks-unhosted.5apps.com">https://drinks-unhosted.5apps.com</a> ETag: "1382694048000" -<span><a href="#section-13" name="section-13">13</a>. Distributed versioning</span> +<span><a name="section-13" href="#section-13">13</a>. Distributed versioning</span> This section is non-normative, and is intended to explain some of the design choices concerning ETags and folder listings. At the @@ -903,7 +907,7 @@ charset=UTF-8","Content-Length":106}}} <span>de Jong [Page 18]</span> -</pre><pre><a href="#page-19" id="page-19" name="page-19"> </a> +</pre><pre><a name="page-19" id="page-19" href="#page-19"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -925,7 +929,7 @@ charset=UTF-8","Content-Length":106}}} but it is up to whichever client discovers a given version conflict, to resolve it. -<span><a href="#section-14" name="section-14">14</a>. Security Considerations</span> +<span><a name="section-14" href="#section-14">14</a>. Security Considerations</span> To prevent man-in-the-middle attacks, the use of https instead of http is important for both the interface itself and all end-points @@ -953,7 +957,7 @@ charset=UTF-8","Content-Length":106}}} <span>de Jong [Page 19]</span> -</pre><pre><a href="#page-20" id="page-20" name="page-20"> </a> +</pre><pre><a name="page-20" id="page-20" href="#page-20"> </a> <span>Internet-Draft remoteStorage December 2014</span> @@ -970,7 +974,7 @@ charset=UTF-8","Content-Length":106}}} The server SHOULD also detect and stop denial-of-service attacks that aim to overwhelm its interface with too much traffic. -<span><a href="#section-15" name="section-15">15</a>. IANA Considerations</span> +<span><a name="section-15" href="#section-15">15</a>. IANA Considerations</span> This document registers the 'remotestorage' link relation, as well as the following WebFinger properties: @@ -980,7 +984,7 @@ charset=UTF-8","Content-Length":106}}} * "<a href="http://tools.ietf.org/html/rfc7233">http://tools.ietf.org/html/rfc7233</a>" * "<a href="http://remotestorage.io/spec/web-authoring">http://remotestorage.io/spec/web-authoring</a>" -<span><a href="#section-16" name="section-16">16</a>. Acknowledgements</span> +<span><a name="section-16" href="#section-16">16</a>. Acknowledgements</span> The authors would like to thank everybody who contributed to the development of this protocol, including Kenny Bentley, Javier Diaz, @@ -993,95 +997,95 @@ charset=UTF-8","Content-Length":106}}} Rick van Rein, Mark Nottingham, Julian Reschke, and Markus Lanthaler, among many others. -<span><a href="#section-17" name="section-17">17</a>. References</span> +<span><a name="section-17" href="#section-17">17</a>. References</span> -<span><a href="#section-17.1" name="section-17.1">17.1</a>. Normative References</span> +<span><a name="section-17.1" href="#section-17.1">17.1</a>. Normative References</span> - [<a id="ref-WORDS" name="ref-WORDS">WORDS</a>] + [<a name="ref-WORDS" id="ref-WORDS">WORDS</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", <a href="http://fakehost/test/bcp14">BCP 14</a>, <a href="http://fakehost/test/rfc2119">RFC 2119</a>, March 1997. <span>de Jong [Page 20]</span> -</pre><pre><a href="#page-21" id="page-21" name="page-21"> </a> +</pre><pre><a name="page-21" id="page-21" href="#page-21"> </a> <span>Internet-Draft remoteStorage December 2014</span> - [<a id="ref-IRI" name="ref-IRI">IRI</a>] + [<a name="ref-IRI" id="ref-IRI">IRI</a>] Duerst, M., "Internationalized Resource Identifiers (IRIs)", <a href="http://fakehost/test/rfc3987">RFC 3987</a>, January 2005. - [<a id="ref-WEBFINGER" name="ref-WEBFINGER">WEBFINGER</a>] + [<a name="ref-WEBFINGER" id="ref-WEBFINGER">WEBFINGER</a>] Jones, P., Salguerio, G., Jones, M, and Smarr, J., "WebFinger", <a href="http://fakehost/test/rfc7033">RFC7033</a>, September 2013. - [<a id="ref-OAUTH" name="ref-OAUTH">OAUTH</a>] + [<a name="ref-OAUTH" id="ref-OAUTH">OAUTH</a>] "<a href="#section-4.2">Section 4.2</a>: Implicit Grant", in: Hardt, D. (ed), "The OAuth 2.0 Authorization Framework", <a href="http://fakehost/test/rfc6749">RFC6749</a>, October 2012. -<span><a href="#section-17.2" name="section-17.2">17.2</a>. Informative References</span> +<span><a name="section-17.2" href="#section-17.2">17.2</a>. Informative References</span> - [<a id="ref-HTTPS" name="ref-HTTPS">HTTPS</a>] + [<a name="ref-HTTPS" id="ref-HTTPS">HTTPS</a>] Rescorla, E., "HTTP Over TLS", <a href="http://fakehost/test/rfc2818">RFC2818</a>, May 2000. - [<a id="ref-HTTP" name="ref-HTTP">HTTP</a>] + [<a name="ref-HTTP" id="ref-HTTP">HTTP</a>] Fielding et al., "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", <a href="http://fakehost/test/rfc7231">RFC7231</a>, June 2014. - [<a id="ref-COND" name="ref-COND">COND</a>] + [<a name="ref-COND" id="ref-COND">COND</a>] Fielding et al., "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests", <a href="http://fakehost/test/rfc7232">RFC7232</a>, June 2014. - [<a id="ref-RANGE" name="ref-RANGE">RANGE</a>] + [<a name="ref-RANGE" id="ref-RANGE">RANGE</a>] Fielding et al., "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests", <a href="http://fakehost/test/rfc7233">RFC7233</a>, June 2014. - [<a id="ref-SPDY" name="ref-SPDY">SPDY</a>] + [<a name="ref-SPDY" id="ref-SPDY">SPDY</a>] Mark Belshe, Roberto Peon, "SPDY Protocol - Draft 3.1", <a href="http://www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3-1">http://</a> <a href="http://www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3-1">www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3-1</a>, September 2013. - [<a id="ref-JSON-LD" name="ref-JSON-LD">JSON-LD</a>] + [<a name="ref-JSON-LD" id="ref-JSON-LD">JSON-LD</a>] M. Sporny, G. Kellogg, M. Lanthaler, "JSON-LD 1.0", W3C Proposed Recommendation, <a href="http://www.w3.org/TR/2014/REC-json-ld-20140116/">http://www.w3.org/TR/2014/REC-json-ld-20140116/</a>, January 2014. - [<a id="ref-CORS" name="ref-CORS">CORS</a>] + [<a name="ref-CORS" id="ref-CORS">CORS</a>] van Kesteren, Anne (ed), "Cross-Origin Resource Sharing -- W3C Candidate Recommendation 29 January 2013", <span>de Jong [Page 21]</span> -</pre><pre><a href="#page-22" id="page-22" name="page-22"> </a> +</pre><pre><a name="page-22" id="page-22" href="#page-22"> </a> <span>Internet-Draft remoteStorage December 2014</span> <a href="http://www.w3.org/TR/cors/">http://www.w3.org/TR/cors/</a>, January 2013. - [<a id="ref-MANIFEST" name="ref-MANIFEST">MANIFEST</a>] + [<a name="ref-MANIFEST" id="ref-MANIFEST">MANIFEST</a>] Mozilla Developer Network (ed), "App manifest -- Revision 330541", <a href="https://developer.mozilla.org/en-">https://developer.mozilla.org/en-</a> US/Apps/Build/Manifest$revision/566677, April 2014. - [<a id="ref-DATASTORE" name="ref-DATASTORE">DATASTORE</a>] + [<a name="ref-DATASTORE" id="ref-DATASTORE">DATASTORE</a>] "WebAPI/DataStore", MozillaWiki, retrieved May 2014. <a href="https://wiki.mozilla.org/WebAPI/DataStore#Manifest">https://wiki.mozilla.org/WebAPI/DataStore#Manifest</a> - [<a id="ref-KERBEROS" name="ref-KERBEROS">KERBEROS</a>] + [<a name="ref-KERBEROS" id="ref-KERBEROS">KERBEROS</a>] C. Neuman et al., "The Kerberos Network Authentication Service (V5)", <a href="http://fakehost/test/rfc4120">RFC4120</a>, July 2005. - [<a id="ref-BEARER" name="ref-BEARER">BEARER</a>] + [<a name="ref-BEARER" id="ref-BEARER">BEARER</a>] M. Jones, D. Hardt, "The OAuth 2.0 Authorization Framework: Bearer Token Usage", <a href="http://fakehost/test/rfc6750">RFC6750</a>, October 2012. - [<a id="ref-AUTHORING" name="ref-AUTHORING">AUTHORING</a>] + [<a name="ref-AUTHORING" id="ref-AUTHORING">AUTHORING</a>] "Using remoteStorage for web authoring", reSite wiki, retrieved September 2014. <a href="https://github.com/michielbdejong/resite/wiki">https://github.com/michielbdejong/resite/wiki</a> /Using-remoteStorage-for-web-authoring -<span><a href="#section-18" name="section-18">18</a>. Authors' addresses</span> +<span><a name="section-18" href="#section-18">18</a>. Authors' addresses</span> Michiel B. de Jong IndieHosters @@ -1104,7 +1108,8 @@ charset=UTF-8","Content-Length":106}}} de Jong [Page 22] -</pre><br></br><span><small><small>Html markup produced by rfcmarkup 1.111, available from +</pre><br> +<span><small><small>Html markup produced by rfcmarkup 1.111, available from <a href="https://tools.ietf.org/tools/rfcmarkup/">https://tools.ietf.org/tools/rfcmarkup/</a> </small></small></span> </div>
\ No newline at end of file |