Opened 17 years ago
Closed 17 years ago
#4416 closed (wontfix)
HttpResponseServiceUnavailable patch
Reported by: | Guilherme Gondim | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Keywords: | ||
Cc: | semente@… | Triage Stage: | Design decision needed |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I need put my site in maintenance, but Django don't have a HttpResponse for http status code 503[1].
In attachment, a simple patch.
Thanks!
Attachments (1)
Change History (4)
by , 17 years ago
Attachment: | httpresponse503.patch added |
---|
comment:1 by , 17 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
It's not clear that creating an extra class for every HTTP response code is a good idea. It's a lot of classes and most of them are just changing one number. Maybe HttpReponse can take a status code param or something.
We need to think about this some more.
comment:3 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I agree with Malcolm; this isn't the right way to handle this.
Note:
See TracTickets
for help on using tickets.
HttpResponse for status code 503 patch