Opened 13 years ago
Closed 13 years ago
#17969 closed Bug (invalid)
Different error page for /static/ URLs
| Reported by: | AlecTaylor | Owned by: | nobody |
|---|---|---|---|
| Component: | HTTP handling | Version: | 1.4 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Strangely during debug of admin CSS not loading I noticed that:
http://localhost:8000/admin/css/base.css
Gave a different error page to:
http://localhost:8000/static/css/base.css
First said:
"f:/projects/store/static\css/base.css" does not exist
Second said:
Using the URLconf defined in urlconf, Django tried these URL patterns, in this order:
<43 numbered lines snipped>
The current URL, admin/css/base.css, didn't match any of these.
Note:
See TracTickets
for help on using tickets.
Different URLs might produce different errors, I don't think that's particularly surprising. If the URL does not match any of your URL patterns, you get the error about no URL pattern found. If the URL matches the STATIC_URL pattern but the static file does not exist, you get the "file does not exist" error. Both are leading to the 404 page, which is the important thing in a production context.
Please in the future, try to first find help in support channels (https://docs.djangoproject.com/en/dev/faq/help/) before creating a ticket.