Russell,
Yeah, I see the inconsistency there, and my first thought was that
this is a bit backward. However, the underlying distinction here is
that it's not the 404 (ie, the resource gone missin') that is the
exception but the Http404 object.
It remains straightforward enough for a developer to
On 29/03/2012, at 12:10 AM, Justin Holmes wrote:
> Russell,
>
> Thanks for the reply.
>
> Two reasons:
>
> 1) Up until now, I hadn't encountered a 404 that had triggered this
> particular process_exception. It hadn't occurred to me that since
> get_object_or_404 actually raises the Http40
Russell,
Thanks for the reply.
Two reasons:
1) Up until now, I hadn't encountered a 404 that had triggered this
particular process_exception. It hadn't occurred to me that since
get_object_or_404 actually raises the Http404 exception that the behavior
was going to be different than, say, a try
On 28/03/2012, at 6:31 AM, Justin Holmes wrote:
> Heretofore, I had always believed that Http404 did not cause Middleware
> process_exception() to be run. Am I right in this thinking?
>
> I have a get_object_or_404 that, when the object in question isn't found, is
> running process_exception.
Heretofore, I had always believed that Http404 did not cause Middleware
process_exception() to be run. Am I right in this thinking?
I have a get_object_or_404 that, when the object in question isn't found,
is running process_exception.
--
Justin Holmes
Head Instructor, SlashRoot Collective
Sl
5 matches
Mail list logo