Opened 8 years ago

Closed 5 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: master
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 8 years ago.
runserver-custom-handler2.diff (3.5 KB) - added by Trevor Caira 8 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)

Changed 8 years ago by Trevor Caira

Changed 8 years ago by Trevor Caira

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 Changed 8 years ago by Alex Gaynor

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Triage Stage: UnreviewedDesign decision needed

comment:2 Changed 6 years ago by Gabriel Hurley

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

comment:3 Changed 5 years ago by Chris Beaven

Severity: Normal
Type: New feature

comment:4 Changed 5 years ago by Jannis Leidel

Easy pickings: unset
UI/UX: unset

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

comment:5 Changed 5 years ago by Jannis Leidel

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