在Django的views.py中将content_type添加到render_to_response中，导致“服务器错误（500）”

Question

在django 1.11中，在views.py中，我正在使用render_to_response函数，如下所示：

return render_to_response(domainObject.template_path, context_dict, context)

这很好。现在，我尝试将此响应的content_type指定为'txt / html'。所以我切换到

content_type = 'txt/html'
return render_to_response(domainObject.template_path, context_dict, context, content_type)

但是使用此设置，服务器将返回一个

服务器错误（500）

按照https://docs.djangoproject.com/en/1.8/topics/http/shortcuts/#render-to-response的文档，我想我以正确的顺序提供了变量...

这里是完整的'def'块供参考：

def myview(request):
        context = RequestContext(request)

                if request.homepage:
                        migrationObject = calltomigration()
                else:
                        integrationObject = Integration.objects.filter(subdomain_slug=request.subdomain).get()
        except ObjectDoesNotExist:
                logger.warning(ObjectDoesNotExist)
                raise Http404

        sectionContent = None
        if not request.homepage:
                sectionContent = getLeafpageSectionContent(referenceObject)

        context_dict = {
                'reference': referenceObject,
                'sectionContent': sectionContent,
                'is_homepage': request.homepage
        }

        #  content_type = 'txt/html'

        return render_to_response(domainObject.template_path, context_dict, context)

这里是NGINX的状态：

● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-01-17 16:34:15 UTC; 40s ago
     Docs: man:nginx(8)
  Process: 14517 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=2)
  Process: 14558 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
  Process: 14546 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
 Main PID: 14562 (nginx)
    Tasks: 2 (limit: 1152)
   CGroup: /system.slice/nginx.service
           ├─14562 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
           └─14564 nginx: worker process

Jan 17 16:34:15 ip-172-31-8-232 systemd[1]: nginx.service: Failed with result 'timeout'.
Jan 17 16:34:15 ip-172-31-8-232 systemd[1]: Stopped A high performance web server and a reverse proxy server.
Jan 17 16:34:15 ip-172-31-8-232 systemd[1]: Starting A high performance web server and a reverse proxy server...
Jan 17 16:34:15 ip-172-31-8-232 systemd[1]: nginx.service: Failed to parse PID from file /run/nginx.pid: Invalid argument
Jan 17 16:34:15 ip-172-31-8-232 systemd[1]: Started A high performance web server and a reverse proxy server.
[1]+  Done                    sudo systemctl restart nginx ```

Answer 1

今天我已解决此问题。我发现在render_to_response中，必须在第三个位置（至少在我正在处理的设置中）指定MIME类型。除PC上的Edge以外，大多数OS /浏览器组合都找出格式错误的MIME类型。立即修复！

Answer 2

标准Django快捷方式功能'render'提供的功能与'render_on_response''相同。 Django的'render_to_reponse'函数在2.2中已弃用，并在3.0中从Django中正式删除。您可以在此处查看发行说明：https://docs.djangoproject.com/en/3.0/releases/3.0/请查看下面的渲染功能的官方文档，https://docs.djangoproject.com/en/3.0/topics/http/shortcuts/另外，context_type应该为“ text / html”，而不是“ txt / html”。