Comment 5 for bug 332061

I agree that looking at the publisher is far more complicated that telling to Paster to ignore it.

However, we can still first tell that to Paster, and let us have more time to figure a clean way in the publisher to remove that exception. I don't think it's the only exception used, and I don't think we can fix it in one night (otherwise it would have been implemented without exception probably, at least at the place we got it). And people are using it as a feature, raise Unauthorized in your code then you don't want the current user to be there (so getting ride of it might be catching it before it get back to the WSGI layer).

And if we say that that issue block the release of Grok 1.0, well, we might prefer the first solution instead of releasing Grok in 6 months.

(I don't say that we should not look at the publisher at all, but we can do both).