294349 - µlaw (.qu) soundfiles build from CGI fails playback on Mac (and on PC)

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[guru66]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

In a system for sound playback, µLaw (.au) files are selected using the
following URL:
http://someserver.my.net/vmail/vmactions.vts?f=play&ext=9821&type=READ&messid=68
This works on MSIE (Mac+Win) + Safari, but fails (with chopping or no sound) on
FireFox on both Mac and Windows.
Playing a .au file that is stored on server disk works.
The Mediaplayer is enabled using the <embed> tag.

Reproducible: Always

Steps to Reproduce:
1.Have a CGI that outputs .au files that takes params and does not have .au in
extension in the CGI-name
2.Create a webpage with an <embed> that links to this CGI.
3. Shoot

Actual Results:  
The mediaplayer of choice is shown, but the sound is chopped to short fragments
and sounds like a "mobile phone out of coverage".

Expected Results:  
Clean soundplay as we get on all other browsers.

<none>

Comment 1

[Anders Conbere]

the url you've posted doesn't seem to be functional (as in nothing loads on it)

Comment 2

[guru66]

Yes, the url -> to a system that is behind a FW. I posted the URL as to show how the URL looks that makes 
FF fail in playing the µLaw soundfiles.
I can check with my client (for which I am involved building this system, and we want FF to work flawlessly 
with it) if we can post a public URL for testing. (This involves setting up a complete Voicemail server)

Comment 3

[Matthias Versen [:Matti]]

How a URL looks like doesn't matter.
The mime-type send by the server and the plugin that you are using to play this
file matters...
And even with this informations it's impossible to do something without a testcase.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.