Re: 1.1rc1 - KeyError in debug.py in technical_404_response

On Aug 5, 9:15 pm, Adam Vollrath wrote: > I'm not sure what the root cause of this is, and I'm really just glad > it's working again.  I'm willing to do more troubleshooting if > prompted by list members.  Perhaps setting django.root to be just a / > was a bad call,

Re: 1.1rc1 - KeyError in debug.py in technical_404_response

I, too, saw this exact stack trace, but when using mod_python. The error did not appear when using the built-in "runserver". Also, it only occurred when requesting a URL beyond the root /. This distinction led me to review my VirtualHost configuration, and I commented out the following line:

Re: 1.1rc1 - KeyError in debug.py in technical_404_response

On Mon, Jul 27, 2009 at 7:48 AM, John P. Speno wrote: > Then ran the server using manage.py runserver. > > telnet localhost 8000 > > typed and entered: GET foo HTTP/1.0 > > And the exception is raised. Trying to GET any resource that doesn't > begin with a slash raises this

Re: 1.1rc1 - KeyError in debug.py in technical_404_response

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

Re: 1.1rc1 - KeyError in debug.py in technical_404_response

On Mon, Jul 27, 2009 at 8:47 PM, John P. Speno wrote: > > 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 >

1.1rc1 - KeyError in debug.py in technical_404_response

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