Opened 5 years ago

Closed 5 years ago

#19978 closed Cleanup/optimization (wontfix)

Technical 500 response as HTML for Ajax request

Reported by: rodrigopmatias@… Owned by: nobody
Component: Core (Other) Version: 1.5
Severity: Normal Keywords: debug 500 error
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I would like to greet everyone, I would also commend the Django project management as well as the team responsible for maintaining this excellent framework that is also my source of income for more than 4 years. In particular I would like to thank Ramigo Morales (@ ramiro) who showed me the way Github to suggest a modification to this excellent project.

I develop a project based on Django that works with 98% of traffic information through Ajax and sintimos miss the old page to debug when an error occurs in development mode. I know that for many the change was positive, but for my team was so bad the search bug.

However I would suggest a modification configurable for compatibility than existed before since for many people must have been positive changes made ​​by the team of Django.

Had implemented the desired modification to this but Ramiro encouraged me to create this ticket. If possible I would like to receive suggestions to modify the implementation so that it better supports the Django project is accepted and maybe in the trunk of this project.

Now appreciate the attention.

pull Request

Change History (1)

comment:1 Changed 5 years ago by Jacob

Resolution: wontfix
Status: newclosed

I really don't like adding another setting for something this domain-specific. You can fairly easily get the same effect with a custom exception middleware; marking wontfix.

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