On Aug 26, 2012, at 10:17 AM, Roberto Galoppini wrote:

> On Sun, Aug 26, 2012 at 1:53 PM, Andrea Pescetti <pesce...@apache.org>wrote:
> 
>> Rob Weir wrote:
>> 
>>> Also, I wonder if it would be worth submitting a patch for Apache.  It
>>> looks like they have the other content types used by OpenOffice, but
>>> not oxt files:
>>> http://svn.apache.org/repos/**asf/httpd/httpd/trunk/docs/**
>>> conf/mime.types<http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types>
>>> 
>> 
>> Actually, it seems it's already been there for a while:
>> $ svn annotate mime.types  | grep oxt
>> 571614   fielding application/vnd.openofficeorg.**extension
>> oxt
>> $ svn log | grep 571614
>> r571614 | fielding | 2007-08-31 23:57:29 +0200(ven, 31 ago 2007) | 3 lines
>> 
>> and if I put an extension on my people.apache.org account I see it's
>> served correctly (of course, this has nothing to do with the problem under
>> discussion; but if problems come from an incorrect MIME type, then people
>> reporting the problem should be able to download
>> http://people.apache.org/~**pescetti/tmp/dict-it.oxt<http://people.apache.org/%7Epescetti/tmp/dict-it.oxt>
>> correctly).
>> 
> 
> I confirm your suspects, it's a MIME config issue. I tested SourceForge
> master, that works just fine, but not all mirrors do manage it correctly.
> As a short-term solution for all extensions - either hosted at SourceForge
> or at third party website - we report the following note:
> 
> *Note: some browsers may download the extension as a .zip file; if this
> happens rename the downloaded file from .zip to .oxt*
> 
> We can then run a communication plan to inform both mirror and
> third-parties.

+1.

I wonder if these are all NGINX servers.

IIRC The ASF requires all Apache Mirrors to use Apache HTTPD Servers, but I'm 
certainly not proposing that GeekNet do the same.

Regards,
Dave



> 
> Roberto
> 
> 
>> 
>> Regards,
>>  Andrea.
>> 
> 
> -- 
> ====
> This e- mail message is intended only for the named recipient(s) above. It 
> may contain confidential and privileged information. If you are not the 
> intended recipient you are hereby notified that any dissemination, 
> distribution or copying of this e-mail and any attachment(s) is strictly 
> prohibited. If you have received this e-mail in error, please immediately 
> notify the sender by replying to this e-mail and delete the message and any 
> attachment(s) from your system. Thank you.
> 

Reply via email to