59
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Configuring the server
Last updated 11/28/2012
Configure Apache for Adobe HTTP Dynamic Streaming
and Apple HTTP Live Streaming
Configure the HTTP modules
Apache HTTP Server that installs with Flash Media Server is configured by default for Adobe HTTP Dynamic
Streaming (to Flash Player and AIR) and Apple HTTP Live Streaming (to iOS and Mac OS). The Flash Media Server
Apache installation includes three custom modules that handle HTTP streaming:
•
jithttp_module—just-in-time on-demand Adobe HTTP Dynamic Streaming (HDS).
•
f4fhttp_module—live HDS; on-demand HDS packaged offline
•
hlshttp_module—live and on-demand Apple HTTP Live Streaming
The configuration of the modules determines the format of the URL that the player requests from the server, the
location of the content, the content fragmentation settings, and other settings. Configure the settings at the server-level
in the Apache httpd.conf file located at
rootinstall
/Apache2.2/conf/httpd.conf. You can also configure some settings
at the application level, event level, and stream level. For complete details, see
Configuring HTTP Dynamic Streaming
and HTTP Live Streaming
in the
Flash Media Server Developer’s Guide
.
For information about configuring ports for HTTP Streaming, see “
Configure ports for HTTP streaming
” on page 6.
Logging for HTTP streaming
All HTTP access requests are logged in the Apache access_log file in the \logs directory. The HTTP Origin Module
doesn’t add any logging directives. All access requests are logged through the standard Apache HTTP Server log
module.
All errors are logged in the Apache error_log file in the \logs directory. The following table shows the response codes
that the HTTP Origin Module returns.
Response code Error message
Description
200
None
No error occurs, and a response has been returned successfully.
304
None
The HTTP Origin Module supports "If-Modified-Since" in the request header
and returns 304 if the file has not been modified."If-Modified-Since" is not
support in requests for manifest files of live events.
400
mod_f4fhttp [400]: Syntax error in %s
mod_hlshttp [400]:Syntax error in %s
Error occurs while parsing the URI request. The variable %s is the URI string.
For example, the request URI http://servername/media/sample- is missing
a fragment number. For example, in the request http://example.com/hls-
vod/sample.f4vNumX.ts, the ts fragment name format is not correct.
400
mod_hlshttp [400]: %1 is a invalid file
Error occurs while reading the information in a file, where %1 is the URI
string. For example, the manifest file is wrong or the bootstrap is invalid or
the .stream file is not valid.
403
mod_f4fhttp [403]: No access to %s
mod_hlshttp[403]: No access to %s
mod_f4fhttp [403]: Internal error %1 (%2)
when processing %3
mod_hlshttp[403]: Internal error %1 (%2) when
processing %3
An error occurs when accessing the file. The variable %s is the file path. For
example, the request URI is http://servername/media/sample.fmf and the
module doesn’t have permission to read the file sample.f4m.
An error occurs when the library fails to access a file. The variable %1 is the
error code from the library, %2 is error description, and %3 is the url string.