Opened 16 years ago

Closed 13 years ago

#10435 closed New feature (fixed)

WSGI handler class cannot be overridden in runserver

Reported by: Trevor Caira Owned by: nobody
Component: Core (Management commands) Version: dev
Severity: Normal Keywords:
Cc: 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

It is currently impossible to use an alternate WSGI handler class than the default django.core.handlers.wsgi.WSGIHandler with the development server. I've included a patch with parameterizes it via an option --handler.

Attachments (2)

runserver-custom-handler.diff (2.9 KB ) - added by Trevor Caira 16 years ago.
runserver-custom-handler2.diff (3.5 KB ) - added by Trevor Caira 16 years ago.
Only accept subclasses of WSGIHandler (this prevents strange issues when the object was found but is not a WSGIHandler). Handle options in such a way that testserver works.

Download all attachments as: .zip

Change History (7)

by Trevor Caira, 16 years ago

by Trevor Caira, 16 years ago

Only accept subclasses of WSGIHandler (this prevents strange issues when the object was found but is not a WSGIHandler). Handle options in such a way that testserver works.

comment:1 by Alex Gaynor, 16 years ago

Triage Stage: UnreviewedDesign decision needed

comment:2 by Gabriel Hurley, 14 years ago

Component: django-admin.py runserverCore (Management commands)

comment:3 by Chris Beaven, 14 years ago

Severity: Normal
Type: New feature

comment:4 by Jannis Leidel, 13 years ago

Easy pickings: unset
UI/UX: unset

This has been fixed in the past by introducing the get_handler method in the BaseRunserverCommand.

comment:5 by Jannis Leidel, 13 years ago

Resolution: fixed
Status: newclosed

Huh, not sure why I haven't set this to fixed.

Note: See TracTickets for help on using tickets.
Back to Top