60
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Configuring the server
Last updated 11/28/2012
Use an external Apache HTTP Server for HTTP Dynamic Streaming and HTTP
Live Streaming
To use an installation of Apache HTTP Server other than the one that installs with Flash Media Server, do the
following:
1
Install Flash Media Server so you can extract the Apache modules.
2
Copy the following files from Flash Media Server to your Apache modules folder:
•
rootinstall
/Apache2.2/modules/adbe_dme.dll
•
rootinstall/Apache2.2/modules/adbe_license.dll
•
rootinstall/Apache2.2/modules/asneu.dll
404
mod_f4fhttp [404]: %s does not exist
mod_hlshttp[404]: %1 does not exist
mod_f4fhttp [404]: Internal error %1 (%2)
when processing %3
mod_hlshttp[404]: Internal error %1 (%2) when
processing %3
An error occurs when the request file is not found. The variable %s is the file
path. For example, the request URI is http://servername/media/sample.fmf
but the file sample.f4m does not exist.
Error occurs when the library fails to find a file. The variable %1 is the error
code from the library, %2 is the error description, and %3 is the url string.
500
mod_f4fhttp [500]: Unknown exception when
processing %1
mod_hlshttp [500]: Unknown error when
processing %1
mod_f4fhttp [500]: Internal error %1 (%2)
when processing %3
mod_hlshttp [500]: Internal error %1 (%2)
when processing %3
mod_hlshttp[500]: Packaging error %1 (%2)
when processing %3
An unknown error occurs when processing a request, where %1 is the URL
string. For example, http://servername/media/sampleSeg1-Frag1,
sampleSeg1.f4f is not a corrupted file.
An unknown error occurs when processing a request, where %1 is the URI
string. The module fails, where %1 is the error code, %2 is error description,
and %3 is the URI string.
Error occurs while packaging a ts segment, where %1 is the error code for
diagnostic purposes, %2 is the error description and %3 is the URI being
processed. An example of an error description is, "Audio format is not
supported".
A packaging error indicates that something went wrong while packaging
the stream data into a ts segment. An internal error indicates that
something went wrong while reading stream data from the recorded f4f
fragments. An internal error is more likely to occur due to a recording
failure than to a play back failure.
503
None
The HTTP Origin Module returns a 503 code so the client and the proxy
servers don’t cache the response.
In a live event, the file can be growing and a fragment could be missing in
one origin server but not missing on another origin server. The HTTP
response header includes an "X-mod_f4fhttp" field to provide more details.
The following is a sample response header:
Date Thu, 04 Mar 2010 06:20:20 GMT Server Apache/2.2.9 (Win32)
Content-Length 432 Last-Modified Wed, 27 Jan 2010 11:43:25 GMT Keep-
Alive timeout=5, max=100 Connection Keep-Alive Content-Type
video/f4f X-mod_f4fhttp 1, error 71
There are two parameters in the X-mod_f4fhttp field delimited by a
comma. The first parameter is a status code and the second parameter is
the error code from the library.
There are two status codes: 1 - The requested fragment number is larger
than the last fragment in the file (the corresponding error is 71). 2 - The
requested fragment number is a missing fragment (the corresponding
error is 34).
Response code Error message
Description