![\"Image](\"http:\/\/www.vskills.in\/lms\/wp-content\/uploads\/2016\/07\/Image-6-14.jpg\")
<\/p>\nIn our URLconf thus far, we\u2019ve defined only a single URLpattern: the one that handles requests to the URL \/time\/. What happens when a different URL is requested?<\/p>\n
To find out, try running the Django development server and hitting a page such as http:\/\/127.0.0.1:8000\/hello\/ or http:\/\/127.0.0.1:8000\/does-not-exist\/, or even http:\/\/127.0.0.1:8000\/ (the site \u201croot\u201d). You should see a \u201cPage not found\u201d message (see Figure 3-2). (Pretty, isn\u2019t it? We Django people sure do like our pastel colors.) Django displays this message because you requested a URL that\u2019s not defined in your URLconf.<\/p>\n
<\/p>\n
The utility of this page goes beyond the basic 404 error message; it also tells you precisely which URLconf Django used and every pattern in that URLconf. From that information, you should be able to tell why the requested URL threw a 404.<\/p>\n
Naturally, this is sensitive information intended only for you, the Web developer. If this were a production site deployed live on the Internet, we wouldn\u2019t want to expose that information to the public. For that reason, this \u201cPage not found\u201d page is only displayed if your Django project is in debug mode. We\u2019ll explain how to deactivate debug mode later. For now, just know that every Django project is in debug mode when you first create it, and if the project is not in debug mode, a different response is given.<\/p>\n\n\n