when to add to mime.types

[Joshua Slive <jo...@slive.ca>]

Anyone want to comment on this issue:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20440

As I say there, I don't have any problem with making an exception to our
policy, or even removing the policy entirely.  But the policy does keep us
from getting a flood of "please add our type" messages.  (We already get a
substantial number.)

Opinions?

Joshua.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org

Re: when to add to mime.types

[Lars Eilebrecht <la...@hyperreal.org>]

According to Yoshiki Hayashi:

> +1.  I don't want to see our config file cluttered with lots
> of 'x-' types.  If it is very popular, it should be
> registered as non 'x-' types.  We don't have problem with
> accepting those official types.  If we accept one 'x-' type,
> it would become harder to reject other private types.  It
> will eventually lead to conflicts of private types.  I don't
> think we should spend time discussing which private types to
> keep in our config.  Don't accpet any private MIME type is
> really a good policy, I believe.

Well, there are already lots of "x-" types in the types config.
E.g., audio/x-mpegurl (m3u) or video/x-msvideo (avi).

IIRC those have been voted in on a case by case basis.

Dunno if the .torrent type is already popular enough to justify
its inclusion. Despite the fact that registering a type with
IANA is not that difficult (file out a form, wait 2-8 weeks
and you are usually done).

just my 0.02

ciao...
-- 
Lars Eilebrecht                - Life is what happens to you while
lars@hyperreal.org          - you are planning to do something else.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org

Re: when to add to mime.types

[Yoshiki Hayashi <yo...@xemacs.org>]

Astrid Keßler <ke...@kess-net.de> writes:

>> As I say there, I don't have any problem with making an exception to our
>> policy, or even removing the policy entirely.  But the policy does keep us
>> from getting a flood of "please add our type" messages.  (We already get a
>> substantial number.)
>
>> Opinions?
>
> Our policy is really ok. It is not too difficult to add additional types
> to the configuration (whereever they want). It seems a lot of people are
> thinking, it is a bug if they have to configure their server.
> <exaggerated>And we would not need AddType if we put all and everything
> to the default mime.types.</exaggerated>

+1.  I don't want to see our config file cluttered with lots
of 'x-' types.  If it is very popular, it should be
registered as non 'x-' types.  We don't have problem with
accepting those official types.  If we accept one 'x-' type,
it would become harder to reject other private types.  It
will eventually lead to conflicts of private types.  I don't
think we should spend time discussing which private types to
keep in our config.  Don't accpet any private MIME type is
really a good policy, I believe.

Just my 2 yen.

-- 
Yoshiki Hayashi

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org

Re: when to add to mime.types

[Astrid Keßler <ke...@kess-net.de>]

> As I say there, I don't have any problem with making an exception to our
> policy, or even removing the policy entirely.  But the policy does keep us
> from getting a flood of "please add our type" messages.  (We already get a
> substantial number.)

> Opinions?

Our policy is really ok. It is not too difficult to add additional types
to the configuration (whereever they want). It seems a lot of people are
thinking, it is a bug if they have to configure their server.
<exaggerated>And we would not need AddType if we put all and everything
to the default mime.types.</exaggerated>

And if it is really so easy to register a new type, no one could say, we 
would obstruct new types from being accepted. If it is not (ok, I didn't 
read the corresponding information),then this might be a reason to easy the 
policy.

Kess

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org

Re: when to add to mime.types

[Hiroaki KAWAI <ha...@bcl.t.u-tokyo.ac.jp>]

Hi.

In my opinion, I think we have only to say them 'please add your mime 
type in your mime.types as you like' or, write it in the documentation. 
Plese think over the case of confliction of 'our types'. How we escape 
the confiction?
So I think our current policy is valid in that sense.

---Hiroaki Kawai

Joshua Slive <jo...@slive.ca> wrote:

> Anyone want to comment on this issue:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20440
> 
> As I say there, I don't have any problem with making an exception to our
> policy, or even removing the policy entirely.  But the policy does keep us
> from getting a flood of "please add our type" messages.  (We already get a
> substantial number.)
> 
> Opinions?
> 
> Joshua.


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org