Summary: | *.cgi pattern should be removed from application/x-cgi | ||
---|---|---|---|
Product: | shared-mime-info | Reporter: | David Faure <faure> |
Component: | freedesktop.org.xml | Assignee: | Jonathan Blandford <jrb> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | alexl, toscano.pino |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
David Faure
2007-12-17 04:50:17 UTC
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.