http://bugs.kde.org/show_bug.cgi?id=153672 A PDF file named foo.cgi, e.g. saved from the web with no suggested filename (content-disposition header iirc), isn't detected as PDF. Would you agree with removing the *.cgi extension for application/x-cgi? The problem is, there isn't any possible magic for application/x-cgi since a cgi is "any executable that is put on a webserver"... In KDE 3 we didn't have a cgi mimetype at all. A cgi is a just a role played by a perl/shell/python/ruby script or by a binary... So the extension doesn't mean much (and the mimetype neither, IMHO).
Ping?
What's the difference with the ASP, or PHP mime-types then? Broken webserver all the same.
The difference is that PHP is an actual programming language. It is actually useful to have a PHP mimetype and to associate *.php files with it. (I believe the same applies to ASP). However CGIs can be anything. From perl to python to C-compiled binaries to shellscript to whatever else one wants to use as the "script that spits out HTML". I cannot see any usefulness in the mimetype application/x-cgi. If foo.cgi is a perl script then it should be detected as application/x-perl, not as application/x-cgi.
Makes sense. * freedesktop.org.xml.in: Remove application/x-cgi mime-type, it's not text/plain (could be a binary), so it should be handled as its real type, as discovered by sniffing (Closes: #13700)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.