[Speex-dev] How to use Speex Cross-Browser, Cross-Platform on Web Pages

Alex S. Brown alexsbrown at alexsbrown.com
Tue Feb 21 21:36:39 PST 2006

As far as a universal solution goes, I am not sure if .spx ought to go with
application/ogg. The politics of standard MIME types and file name extensions
is simply beyond me. I do know that Speex has its own MIME type
(audio/x-speex), and the .spx file extension goes with it.

For my particular situation, I am assuming that I have no control over each
person's browser. I am just writing my web pages and serving them up. I can
control MIME types and file extensions, but my users might not be able to use
some of them.  I can recommend plug-ins to download and install, but generally
I want my web pages to work without any configuration changes by the user. If
possible, no plug-ins is ideal. If a plug-in is needed, it is best if the
browser can detect a compatible plug-in based on the MIME type. Asking the
users to fiddle with MIME configurations is probably asking too much, and I
will lose my audience.

Unfortunately, all this requires getting the browser and plug-in makers to
support Speex better. So I will keep posting my bug/feature requests to


Quoting Ralph Giles <giles at xiph.org>:

> On Tue, Feb 21, 2006 at 08:44:32PM -0500, Alex S. Brown wrote:
> > I spent some more time with the Ogg and Speex format specs, and I realized
> that
> > using the "application/ogg" MIME type is technically sound, since Speex is
> > contained in an Ogg wrapper. To get full browser support, though, it is
> best to
> > rename it so its file extension is "ogg". Some browsers do not support
> files
> > where the MIME type and file extension are different, based on security
> > concerns.
> Wouldn't it make more sense to register .spx as an extension for the 
> application/ogg mime-type in the browser?
>  -r

Alex S. Brown, PMP
alexsbrown at alexsbrown.com

More information about the Speex-dev mailing list