Re: [whatwg/fetch] Describe filtered responses better (PR #1513)

@domenic commented on this pull request.



> +that offers a limited view on an associated <a for=/>response</a>. This associated
+<a for=/>response</a> can be accessed through <a>filtered response</a>'s associated
+<dfn export id=concept-internal-response for="filtered response">internal response</dfn> (a
+<a for=/>response</a> that is neither a <a for=/>network error</a> nor a
+<a for=/>filtered response</a>).
+
+<p>Unless stated otherwise a <a for=/>filtered response</a>'s associated concepts (such as its
+<a for=response>body</a>) refer to the associated concepts of its
+<a for="filtered response">internal response</a>. (The exceptions to this are listed below as part
+of defining the concrete types of <a for=/>filtered responses</a>.)
+
+<div class=note>
+ <p>The <a for=/>fetch</a> algorithm returns such a view to ensure APIs do not accidentally leak
+ information. If the information needs to be exposed for legacy reasons, e.g., to feed image data to
+ a decoder, the associated <a for="filtered response">internal response</a> can be used, which is
+ only "accessible" to internal specification algorithms.

I stil find this sentence confusing them... what is an example of a non-internal specification algorithm, which doesn't have access?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1513#discussion_r1003838705
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1513/review/1153906374@github.com>