Optimizing Apache/PHP for Helioviewer

Keith — Thu, 02 Sep 2010 12:42:03 GMT

Manually specifying MIME type using PHP:

←Older revision		Revision as of 12:42, 2 September 2010
(4 intermediate revisions not shown.)
Line 3:		Line 3:

	= Apache =		= Apache =
		+	== Caching ==
		+	== MIME types ==
		+	In order to function optimally, Apache should be configured to set the proper content type for all of the kinds of files it deals with. For many of the more commonly-used file types such JPEG, PNG, and MP4, the server likely already knows which content type to use. For some other types, however, such as JPEG 2000 images, and Ogg Theora and WebM videos, Apache may not know how to properly serve these files.
		+
		+	=== Testing MIME type support ===
		+	Firebug can be used to check what headers Apache returns for different image and movie types. To do this, simply attempt to load the desired file in HTML. Open Firebug and go to "Net" -> "Headers" -> "Response Headers". Content-type should appear there. If Apache does not recognize the image/movie then it will likely be returned as "text/plain". If Apache does recognize the resource then you should see the correct MIME type, e.g. "video/webm".
		+
		+	Note that if you see "304 Not Modified" next to the request status, then the resource is being pulled from cache and the HTTP headers may not reflect any changes you have made to Apache's configuration. You can use "Control + F5" to force Firefox to re-fetch all cached items.
		+
		+	=== Adding support for new file types to Apache ===
		+
		+	To enable Apache to recognize new MIME types, you can use the "AddType" directive in either an Apache configuration file (e.g. httpd.conf or apache2.conf), or in an .htaccess file:
		+
		+	<pre>
		+	# Add support for JP2, WebM, etc
		+	AddType video/ogg .ogv .ogg
		+	AddType video/webm .webm
		+	AddType image/jp2 .jp2
		+	AddType image/jpx .jpx
		+	</pre>
		+
		+	=== Manually specifying MIME type using PHP ===
		+
		+	In the case where a file is being returned by PHP, rather than being accessed directly, it is also possible to manually specify the MIME type to use. For many file types, this can be automated using the [http://www.php.net/manual/en/book.fileinfo.php PHP's FileInfo class], e.g.:
		+
		+	<source lang="php">
		+	<?php
		+	$fileinfo = new finfo(FILEINFO_MIME);
		+	header("Content-type: " . $fileinfo->file("file.mp4"));
		+	?>
		+	</source>
		+
		+	However, PHP may also fail to recognize many of the newer formats. To see what is supported, try printing out the MIME types for various files, e.g.:
		+
		+	<source lang="php">
		+	<?php
		+	$fileinfo = new finfo(FILEINFO_MIME);
		+	echo "MP4: " . $fileinfo->file("h264.mp4") . "<br>";
		+	echo "Mov: " . $fileinfo->file("h264.mov") . "<br>";
		+	echo "Ogg: " . $fileinfo->file("theora.ogg") . "<br>";
		+	echo "VP8: " . $fileinfo->file("vp8.webm") . "<br>";
		+	echo "JP2: " . $fileinfo->file("image.jp2") . "<br>";
		+	echo "JPX: " . $fileinfo->file("imageseries.jpx");
		+	?>
		+	</source>
		+
		+	The desired output should be:
		+
		+	<pre>
		+	MP4: video/mp4
		+	Mov: video/quicktime
		+	Ogg: video/ogg
		+	VP8: video/webm
		+	JP2: image/jp2
		+	JPX: image/jpx
		+	</pre>
		+
		+	If PHP does not recognize all of the file types you may instead see something like:
		+
		+	<pre>
		+	MP4: video/mp4
		+	Mov: video/quicktime
		+	Ogg: application/ogg
		+	VP8: application/octet-stream
		+	JP2: application/octet-stream
		+	JPX: application/octet-stream
		+	</pre>
		+
		+	In this case, the simplest solution is simply to add checks for the file types that PHP does not recognize and specify those content types manually.

	= PHP =		= PHP =

Helioviewer Wiki - Recent changes [en]

Optimizing Apache/PHP for Helioviewer