Hi,
On Fri, Jan 03, 2014 at 12:56:44PM -0600, Michael Lustfield wrote: > On Fri, Jan 3, 2014 at 9:03 AM, Toni Mueller <supp...@oeko.net> wrote: > > Why? I am only aware of its usefulness in conjunction with the XSLT > > module. > Because nginx-full is the package for the "full" version of the nginx > binary. It will not have configuration files in it. This is what > nginx-common is for. It's for files that are common among the versions of > nginx binaries. hmmm... ok. > > http://nginx.org/en/docs/http/ngx_http_xslt_module.html#xml_entities > > > I'm not familiar with this module. What are the chances that admins will > want to change this file? Will the defaults suffice for anyone/everyone > (the 99.99%)? My estimate is that at least everyone who wants to proxy to Plone and use XSLT, will need it. I arrived at this conclusion because I got site-breaking errors without it (libxml2 parse errors in the middle of the page and 404s for pages that definitely exist). IOW, if you are an XSLT user, I suspect that you will need such a file unless your web pages are generated to contain no &somesymbol; type entity references at all. I don't know what the default values that nginx (libxml2, to be specific) knows about w/o having such a file, are. Although I likely have no use for the bulk of the entries in that file, simply implementing the entire standard was easier and safer than picking a subset and shipping that. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
