On Thursday 11 October 2012, Charles Plessy wrote: > Le Mon, Oct 08, 2012 at 03:38:10PM +0200, Ondřej Surý a écrit : > > Just one last question which came to my mind. Would this all be > > fixed if we added non-magic type to mime-support (e.g. > > http://bugs.debian.org/670945) and reverting the changes done in > > the php5-cgi package? > > > > That I think would justify change in the mime-support package. > > Too much breakage on every front now.
And remove the php-cgi.conf completely, right? So this would introduce a different fix for the multi-views problem. Are you sure that there is no other problem that we would re-introduce? Maybe it's worth a try. > Hello Ondřej, Stefan, and everybody, > > Do you think that there is a way to fix #589384 (the *.php.foo > problem) without removing the application/x-httpd-* media types ? There is at least no solution that is obviously right. I fear that regardless what we do, we will break some configs. Besides removing the media types from /etc/mime.types, one could add a "RemoveType php ..." to the apache config (but where?). Or maybe, one could also set "AddHandler default-handler php ...". The latter is an idea I just had, I have not thought it through or tested it. > I did not realise before that in the current release cycle, Apache > stays at version 2.2 and that in Jessie, configurations will need > to be re-adjusted anyway. I think that it is a good argument for > a compromise, provided that #589384 stays solved and that we agree > that in Jessie the media types application/x-httpd-* will be > removed from /etc/mime.types. > > Of course, it is even better if there is an easy way to adjust the > priority of the SetHandler statement of php5_cgi.conf in a way > that does not break FastCGI configurations. I think there are rather too many possibilities and the pros/cons of each one get lost in this thread. (Well, that is partially my fault because I take so long to respond, but I have been busy :-( ) Maybe it would be better to create a single document with all possible solutions and pro and cons? I have started to create such an overview at http://wiki.debian.org/Apache/WheezyMimeTypes but it is not finished yet. Feel free to add more infos/solutions/pros/cons. The page may come in handy for the Jessie, too. Christoph: For mod-fastcgi/mod-fcgid, the file.fcgi.foo problem is somewhat mitigated that they require "Options ExecCGI", too. And AFAICS that is not set by default. Any opinions if this is "good enough" for wheezy? I lean towards yes, but maybe I am missing something. Besides, it would be interesting to check how mod_action behaves... Cheers, Stefan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
