Opened 16 years ago
Closed 16 years ago
#6278 closed (fixed)
Document that 404 has RequestContext and 500 doesn't
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | 404 500 | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Just figured this out the hard way so I thought I'd supply some documentation...
404 is rendered with RequestContext and 500 is passed an empty Context({}).
Attachments (1)
Change History (3)
by , 16 years ago
| Attachment: | 404_500_docs.diff added |
|---|
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Ready for checkin |
|---|
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [7081]) Fixed #6278 -- Documented that the 404 template is passed a RequestContext and the 500 handler is not. Thanks, Rob Hudson.