@@ -337,21 +337,6 @@ <h2>Network requests</h2>
337
337
A < a > network request</ a > is < dfn data-lt ="fail "> failed</ dfn > if it is not
338
338
< a > successful</ a > .
339
339
</ p >
340
-
341
- < p >
342
- < a > Network error reports</ a > are < strong > NOT</ strong > < a > visible to
343
- < code > ReportingObserver</ code > s</ a > .
344
- </ p >
345
-
346
- < p class ="note ">
347
- < a > Network error reports</ a > are not < a > visible to
348
- < code > ReportingObserver</ code > s</ a > because they are only intended to be
349
- visible to the administrator or owner of the server < em > receiving</ em > the
350
- requests. If they were < a > visible to < code > ReportingObserver</ code > s</ a > ,
351
- then the reports would also be visible to the < em > originator</ em > of the
352
- request. For cross-origin requests, this could leak information about the
353
- server's network configuration to parties outside of its control.
354
- </ p >
355
340
</ section >
356
341
357
342
< section >
@@ -395,6 +380,35 @@ <h2>Network errors</h2>
395
380
</ p >
396
381
</ section >
397
382
383
+ < section >
384
+ < h2 > Network error reports</ h2 >
385
+
386
+ < p >
387
+ A < dfn data-lt ="network error reports "> network error report</ dfn > is a < a
388
+ data-cite ="!REPORTING "> Reporting API</ a > < a > report</ a > that describes a
389
+ < a > network error</ a > .
390
+ </ p >
391
+
392
+ < p >
393
+ < a > Network error reports</ a > have a < a > report type</ a > of
394
+ < code > network-error</ code > .
395
+ </ p >
396
+ < p >
397
+ < a > Network error reports</ a > are < strong > NOT</ strong > < a > visible to
398
+ < code > ReportingObserver</ code > s</ a > .
399
+ </ p >
400
+
401
+ < p class ="note ">
402
+ < a > Network error reports</ a > are not < a > visible to
403
+ < code > ReportingObserver</ code > s</ a > because they are only intended to be
404
+ visible to the administrator or owner of the server < em > receiving</ em > the
405
+ requests. If they were < a > visible to < code > ReportingObserver</ code > s</ a > ,
406
+ then the reports would also be visible to the < em > originator</ em > of the
407
+ request. For cross-origin requests, this could leak information about the
408
+ server's network configuration to parties outside of its control.
409
+ </ p >
410
+ </ section >
411
+
398
412
< section >
399
413
< h2 > NEL policies</ h2 >
400
414
0 commit comments