404 not 500 ?

Hi I'm at the end of this first lesson. When you say:

"Run the server again and hit the homepage. It’s blank because it’s serving the 500.html. This points to a likely culprit, which is that we don’t have a catch-all URL route."

is this a mistake?

When hitting the homepage I get a 404 -both locally and on Heroku, e.g. [28/Mar/2013 12:30:56] "GET / HTTP/1.1" 404 74

(I'm using Django 1.5)

Sorry You must be a logged in, registered user to answer a question.

Answers

No, it should definitely be throwing a 500 because of not finding an applicable route.

kennethlove (Staff) on
Yeah, Jolly we had the same issue, we believe the same as you, is because django 1.5.1, sorry for the spaninglish. Thanks Kenneth, me and my little brother are very grateful. Greetings from Medellín !
ouuyeah on
I definitely got 404 at this point, both locally and on Heroku, perhaps it's a difference with Django 1.5, I hope so :)
jollyfellow on