-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show Traceback HTML in browsable API #4172
Conversation
I haven't dug into it, but I don't believe this would resolve the issue - the problem is likely not that the 500 page isn't returned, but that that it isn't handled correctly and rendered by the browsable API. If you can confirm that you've ensure the behavior changes before and after this patch, then I'll reopen the ticket, and consider it further. |
@tomchristie The 500 page is returned as plain text. In the JS, if response is not html it will redirect. We can handle it in JS side, but the response will be plain text. To generate the original django error page, we need to do this. I tested this by creating a sample app and its working. Please see the attachment. |
Thanks for that. |
Current coverage is 91.43%
|
Looks great, yup! Excellent work. 😄 |
Closes #4042