Supplemental Info from my developer:
Regarding any correspondence you may have with Adobe about our flash
11.4 problem, I spent all evening doing packet captures and changing
experimental server code in an attempt to find a way to avoid
triggering the flash 11.4 problem.
Fortunately, I did discover something interesting/useful.
Whenever live audio is streamed from an HTTP server, it is standard
practice (in widespread use) for the server to NOT include a
Content-Length field in the HTTP response header, because if it is a
live stream, there is no way to know how long the stream will be at the
point that the stream starts.
After exhaustive testing this evening, the only way I could get a live
stream to play with Firefox on Windows/7 directly with flash 11.4 was
to include a Content-Length: header field with a bogus somewhat-large
value. In that case it works, at least testing with the flash player
that I experimented with last night.
I don't plan to make a change to our server if we have any other
solution available to us, because such a change is known to be wrong
for other cases. For example, no matter what I set the Content-Length
value to, if the webcast ever reaches that size, the stream would stop
playing right there. If we make the Content-Length super-huge, then the
navigation slider won't work, but at least the live streaming audio
plays with at least Windows Firefox 15 and flash 11.4.
It may be of help for Adobe to know that if a Content-Length: header is
supplied, that it materially effects the occurrence of the problem, so
please feel free to pass this along to Adobe.
