On Jul 27, 9:08 am, Russell Keith-Magee
wrote:
> That's certainly one possible solution. However, I suspect a better
> solution would be to find the place that is raising an 404 exception
> that isn't populating the 'tried' attribute. Can you help out by
> telling us the conditions that lead to y
Hi,
Running Django 1.1rc1 via wsgi. Here's the stdout including the
request that raised the exception:
125.65.165.139 - - [26/Jul/2009 23:02:46] "GET
http://pv.wantsfly.com/prx.php?hash=65B15474B46964654834EDB41F4020883D0D9A08F7F9
HTTP/1.0" 500 59
Traceback (most recent call last):
File "/usr/
