(In reply to comment #41)
> The thing is, content policy has a built-in notion of different sorts of
> blocking... You can block a server, or a request, or a type, and we handle
> those a bit differently in terms of whether we, e.g., show alt text.
I'm not sure how that's relevant to this proposal. All I'm suggesting is to allow overriding to always-ACCEPT for a given URI. I can't think of a use case that involves overriding a policy to change the rejection type.
(In reply to comment #41)
> The thing is, content policy has a built-in notion of different sorts of
> blocking... You can block a server, or a request, or a type, and we handle
> those a bit differently in terms of whether we, e.g., show alt text.
I'm not sure how that's relevant to this proposal. All I'm suggesting is to allow overriding to always-ACCEPT for a given URI. I can't think of a use case that involves overriding a policy to change the rejection type.