Mailinglist Archive: opensuse-bugs (15049 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=216934#c3


Sierk Bornemann <sierkb@xxxxxx> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
                 CC|                                                |poeml@xxxxxxxxxx, sierkb@xxxxxx
                URL|http://www.rfc-editor.org/rfc/rfc4329.txt       ;|http://www.rfc-editor.org/rfc/rfc4329.txt,
                   |                                                |http://issues.apache.org/bugzilla/show_bug.cgi?i
                   |                                                |d=40299#c3
             Status|RESOLVED                                        |REOPENED
         OS/Version|SuSE Linux 10.1                                 |openSUSE 10.3
           Priority|P5 - None                                       |P2 - High
         Resolution|FIXED                                           |




--- Comment #3 from Sierk Bornemann <sierkb@xxxxxx>  2007-09-12 07:06:36 MST ---
Please update /etc/mime.types to sync with IANA registry and with mime.types of
Apache2 of apache.org.

See also the latest changes of stable Apache 2.2.6 on
http://www.apache.org/dist/httpd/CHANGES_2.2.6:
[..]

*) mime.types: Many updates to sync with IANA registry and common
   unregistered types that the owners refuse to register.  Admins
   are encouraged to update their installed mime.types file.
   PR: 35550, 37798, 39317, 31483 [Roy T. Fielding]

*) mime.types: add Registered Javascript/ECMAScript MIME types (RFC4329)
   PR 40299 [Dave Hodder <dmh dmh.org.uk>]
[..]

Extension for application/ecmascript:

Please also have a close look especially at
http://issues.apache.org/bugzilla/show_bug.cgi?id=40299 and
http://issues.apache.org/bugzilla/show_bug.cgi?id=40299#c3

which trys to solve a conflict between the official IANA registered RFC and
real world needs.
Concerning that conflict -- do you tend to follow the official proposed IANA
extension .es or the one apache.org now has introduced in their mime.types with
ecma?
I am not happy with Apache introducing a new extension .ecma, which differs
from the official proposed .es from IANA, and I think, it would be *very*
helpful to correspondend with the responsible people of apache.org and other
Linux/Unix distributors to solve this conflict in a *unique* way to avoid
uncertainty concerning the right use of extension for ECMAScript.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.