Re: [Kimchi-devel] [PATCH] Issue #<570: Make nginx proxy optional

On 12/03/15 02:50, Aline Manera wrote: As long as someone uses a proxy (or some other way to make it accessible like using it on a desktop, or SSH port forwards) Kimchi just works, there's nothing special about nginx. WRT that the X-* options are sensible, but cherrypy shouldn't be setting HSTS since it can't know if it'll be proxied using TLS. Obviously for the websockets based console to work it'll need to be via TLS. I've updated my patch to include them and will resend it, I could also look at setting them on the Kimchi side as well. I don't think that's a real problem, the users likely to want to run their own proxy are those who would (predominantly at least) already know what they want to use, and how to configure it. Novice users will simply keep the default setting and continue using nginx unchanged. The inclusion of an apache2 configuration snippet is two-fold, first, it's the most common web server still and thus the most likely to be wanted as a proxy; second, being the most common it's common for other web servers to include a translation of apache terms in their documentation, or documents that others write.