On 27/01/2014 09:50, Jonathan Matthews wrote:
> On 27 January 2014 02:49, Some Developer <someukdeveloper@gmail.com> wrote:
>> Seems a bit strange to me that an application framework sets HTTP headers.
>> Surely this should be left to the HTTP server? What are other peoples
>> opinions on this?
> There are many instances where the application is the most
> knowledgable layer regarding which HTTP headers to send: think
> caching; think keep-alive. In general, the absolute /least/ you can do
> in the reverse-proxy layer, the better. IMHO.
>
> J
>
Fair enough. It would be somewhat easier to manage if all headers were
implemented in one place or the other. If I could set arbitary headers
in Django then I could do it all there but at the moment I have some
headers set in my Nginx configuration and some headers that appear to be
set in Django and that just makes it confusing.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx