id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
37207	Add a backend setting to enforce HTML response for technical 500 errors	Aswanth V C		"Following the improvements to content type negotiation for the 500 error response in Ticket #36456 (django.views.debug.technical_500_response), the error response is now being converted to plain text in certain scenarios based on the request's preferred type.

This behavior change makes debugging more difficult for existing systems that rely on receiving an HTML response by default (for example, utilizing the HTML response within Chrome DevTools' Inspect tab).

Updating the requested content type across various existing frontend applications is time-consuming and risks breaking existing logic, especially where frontend conditions directly depend on the request's content type.

To resolve this and support existing workflows, we should provide a backend setting that allows developers to explicitly prefer or enforce an HTML response for technical 500 errors, bypassing the strict content-type negotiation when needed."	New feature	closed	Error reporting	6.0	Normal	wontfix		Aswanth V C	Unreviewed	0	0	0	0	0	0