it's possible that the body of a 451 HTTP response contains javascript or something else to redirect away from the blocked resource. in that case, the user doesn't have a chance to see the 451 icon light up, or to click on it and report.
we need to think about UX/workflow more clearly.
it's possible that the body of a 451 HTTP response contains javascript or something else to redirect away from the blocked resource. in that case, the user doesn't have a chance to see the 451 icon light up, or to click on it and report.
we need to think about UX/workflow more clearly.