{"id":16658,"date":"2015-08-18T05:01:50","date_gmt":"2015-08-17T19:01:50","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=16658"},"modified":"2019-04-27T14:16:04","modified_gmt":"2019-04-27T04:16:04","slug":"php-content-type-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/php-content-type-primer-tutorial\/","title":{"rendered":"PHP Content Type Primer Tutorial"},"content":{"rendered":"
\"PHP<\/a>

PHP Content Type Primer Tutorial<\/p><\/div>\n

Today we want to start a discussion on a big topic in web programming, the webpage content type (or mime type<\/a>).<\/p>\n

The normal association of webpages is with the …<\/p>\n


\ntext\/html
\n<\/code><\/p>\n

… mime type. Server side languages such as PHP and ASP.Net, for the most part, create webpages in HTML format, but they don’t have to. Supposing you have some PDF data then you can use PHP’s header method to use (the snippet from today’s PHP php_content_type.php<\/a>) …<\/p>\n


\n<?php
\n\/\/ ...
\n\/\/ no echo statements anywhere up here
\n\/\/ ...
\n header<\/a>('Content-Type: ' . $ct);
\n echo file_get_contents<\/a>(urldecode<\/a>($_POST['selname']));
\n?>
\n<\/code><\/p>\n

… to show a webpage using a mime type defined by the PHP variable $ct which is “application\/pdf” in the URL “http:\/\/localhost:888\/logo.pdf” of our example tutorial picture<\/a>.<\/p>\n

We show this distinction today by writing a PHP web application that in the first instance is a web page consisting of an HTML form as per …<\/p>\n


\n<form target='_blank' action='.\/php_content_type.php' method='POST'>
\n...
\n<\/code><\/p>\n

… the “target=’_blank'” of which is ensuring a new webpage will be opened and by saying “method=’POST'”, on submission, would POST (into $_POST[‘selname’]) to itself (in a new webpage) the HTML input type=url as per …<\/p>\n


\nUrl: <input type='url'<\/a> name='selname' id='selname' style='width:70%;' value='HTTP:\/\/www.rjmprogramming.com.au\/MyBusinessUnidad\/Welcome_files\/logo.jpg'><\/input>
\n...
\n<\/code><\/p>\n

… the user defined URL of interest.<\/p>\n

In the second instance, or the callback<\/a> scenario, the php_content_type.php<\/a> code analyzes $_POST[‘selname’] to derive a file extension (if none, would assume a mime type of text\/html). That file extension we map against the very useful sitepoint<\/a> resource we thank very much to arrive at a suitable mime type to be suitable for that PHP $ct variable we talked about earlier. This gives us the scenario used for the middle of three buttons …<\/p>\n

    \n
  1. Navigate via Web Browser … up at the web browser address bar you’ll see the Url of your data source<\/li>\n
  2. Show via PHP Content Type to New Webpage … up at the web browser address bar you’ll see the Url of php_content_type.php (which got POSTed to … so no $_SERVER[‘QUERY_STRING’] even)<\/li>\n
  3. Show PHP Content Type Below … ie. to an HTML iframe<\/a>, the scenario of today’s tutorial picture<\/a><\/li>\n<\/ol>\n

    With scenarios 2 and 3 above there is no hope that View->Page Source nor This Frame->View Page Source will result in a happy readable result, where scenario 1 will sometimes allow for this.<\/p>\n

    With this knowledge in mind, or by trying a live run<\/a>, maybe now, some of the mystifying address bar URLs you encounter surfing the net may be more explainable to you … hope so. Understanding of this topic can be a “light bulb” moment for many people, and a little bit of patience can reveal many possibilities with web applications, should you delve deeper yourself.<\/p>\n

    If this was interesting you may be interested in this<\/a> too.<\/p>\n