A fetch blocked by data-loss-prevention policy is now distinguishable from an ordinary network failure.
What's wrong with this entry?
A failed content fetch can now be tagged isDlpDenied alongside the existing detail, status and timeout fields, so a block by data-loss-prevention policy is distinguishable from an ordinary network failure. The name is new in this build.
isDlpDenied
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
WebFetch refuses redirects that leave a trusted docs path
Both mention fetch
-
v2.1.232
Fetched pages are wrapped in an untrusted-content envelope
Both mention fetch
-
v2.1.232
WebFetch reports which local files a fetch actually wrote
Both mention fetch