HTTP Web-Sniffer 1.0.36 by Lingo4you - Sprachen Online Lernen

View HTTP Request and Response Header

For more information on HTTP see RFC 2616

HTTP(S)-URL: (IDN allowed)

HTTP version:

• Request type:

HTTP Request Header

Connect to 65.254.248.135 on port 80 ... ok

GET /test.php HTTP/1.1[CRLF]
Host: jp29.org[CRLF]
Connection: close[CRLF]
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de-de) AppleWebKit/523.10.3 (KHTML, like Gecko) Version/3.0.4 Safari/523.10[CRLF]
Accept-Encoding: gzip[CRLF]
Accept-Charset: ISO-8859-1,UTF-8;q=0.7,*;q=0.7[CRLF]
Cache-Control: no[CRLF]
Accept-Language: de,en;q=0.7,en-us;q=0.3[CRLF]
Referer: http://web-sniffer.net/[CRLF]
[CRLF]

HTTP Response Header

NameValueDelim
Status: HTTP/1.1 200 OK
Date:Thu, 02 Sep 2010 14:53:33 GMT
Content-Type:application/xhtml+xml
Connection:close
Server:Apache
X-Powered-By:PHP/5.2.12
Vary:Negotiate,Accept
Content-Length:14266

Content (13.93 KiB)

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en-US' lang='en-US'>
  <head profile="http://www.w3.org/2003/g/data-view">
    <title>
      Problems serving XHTML 1.0 Web Pages
    </title>
    <meta http-equiv="Content-Type" content="negotiate; charset=utf-8" />
    <meta name="language" content="en-US" />
    <meta name="description" content="A test page for producing XHTML 1.0 Web Pages and serving them via content negotiation" />
    <meta name="keywords" content="XHTML, production, MIME, Content-Type, negotiation, PHP, Server-side" />
    <link rel="shortcut icon" href="/favicon.ico" />
    <link href="ppagesb.css" rel="stylesheet" type="text/css" />
    <link rel="alternate" type="application/rss+xml" title="JFP RSS" href="pprss.rdf" />
    <link href="pprss.rdf" rel="rss" type="application/rdf+xml" />
    <link href="ppdc.rdf" rel="meta" type="application/rdf+xml" />
    <link rel="transformation" href="http://www.w3.org/2000/06/dc-extract/dc-extract.xsl" />
    <link rel="schema.DC" href="http://purl.org/DC/elements/1.1" />
    <meta name="DC.Contributor" content="BAP" />
    <meta name="DC.Coverage" content="Producing and Serving XHTML 1.0 Web Pages" />
    <meta name="DC.Creator" content="JFP" />
    <meta name="DC.Date" content="last update: 2009-01-20" />
    <meta name="DC.Description" content="Problems producing and serving XHTML 1.0 Web Pages with the appropriate MIME type" />
    <meta name="DC.Format" content="size: approx. 20.00kb" />
    <meta name="DC.Identifier" content="XHTML 1.0 via content negotiation" />
    <meta name="DC.Language" content="en-us" />
    <meta name="DC.Publisher" content="JFP" />
    <meta name="DC.Relation" content="Markup Language" />
    <meta name="DC.Rights" content="Creative Commons Attribution 3.0 United States License" />
    <meta name="DC.Source" content="W3C" />
    <meta name="DC.Subject" content="XHTML, MIME, Content-Type, negotiation, PHP, Server-side" />
    <meta name="DC.Title" content="Producing and serving XHTML 1.0 Web Pages" />
    <meta name="DC.Type" content="Web Document" />  
  </head>
  <body>
    <h1>
      PROBLEMS SERVING XHTML 1.0 WEB PAGES
    </h1>
    <div id="box">
      <div id="content">
        <p>
          <em>This is an XHTML 1.0 (Strict) Web Page served via content-negotiation 
          (PHP on the Server side) as Media (MIME) type <em>application/xhtml+xml</em> 
          <a href="http://www.rfc-editor.org/rfc/rfc3236.txt">(RFC3236)</a> with 
          XML declaration to Browsers that recognize that MIME type and as Media (MIME) 
          type <em>text/html</em> <a href="http://www.rfc-editor.org/rfc/rfc2854.txt">(RFC2854)</a> 
          without XML prolog declaration to Microsoft Internet Explorer Browsers.</em>
        </p>
        <p>
          <strong>Producing XHTML 1.0 Web Pages:</strong>
        </p>
        <p>
          There are numerous problems and pitfalls involved in producing XHTML 1.0 
          Web Pages - particularly those intended to comply with <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/#guidelines">
          Appendix C of the W3C XHTML 1.0 Recommendation</a> which are therefor 
          really <em>HTML rather than XHTML Web Pages</em>. Practically 
          all extant XHTML 1.0 pages are  being produced in this manner. 
          XHTML 1.0 Web Pages <em>should really provide XML 
          functionality</em> as prescibed by the Recommendation. 
          <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">W3C XHTML 1.0 
          Recommendation (Second Edition)</a> includes the syntax, constructs 
          and guidelines.
        </p>
        <p>
          <strong>Important considerations for Web Authors:</strong>
        </p>
        <p>
          Web Authors wishing to produce optimally performing and conforming
          XHTML 1.0 Web Pages should consult the following References and 
          Resources before they embark on actual page production:
        </p>
        <ul>
         <li>
           <a href="http://www.w3.org/International/articles/serving-xhtml/">
           W3C page on Serving XHTML 1.0</a>
         </li>
         <li>
            <a href="http://hixie.ch/advocacy/xhtml">Sending XHTML as text/html 
            Considered Harmful</a>
         </li>
         <li>
            <a href="http://www.456bereastreet.com/archive/200501/the_perils_of_using_xhtml_properly/">
            The perils of using XHTML properly</a>
         </li>
         <li>
           <a href="http://hsivonen.iki.fi/doctype/">Activating Browser Modes with Doctype</a>
         </li>
        </ul>
        <p>
          <strong>Serving XHTML 1.0 Web Pages as Media type <em>application/xhtml+xml</em>:</strong>
        </p>
        <p>
          XHTML 1.0 Web Pages <strong>should</strong> be served as Media type 
          <em>application/xhtml+xml</em> to have XML functionality as prescibed 
          by the Recommendation. The W3C Document <a href="http://www.w3.org/TR/xhtml-media-types/">
          XHTML Media Types - Second Edition</a>: <em>Serving the Most 
          Appropriate Content to Multiple User Agents from a Single Document 
          Source - W3C Working Group Note 16 January 2009</em> <strong>(work 
          in progress draft document)</strong> provides suggestions and 
          guidance relating to the delivering of XHTML Documents. However, as the 
          Note points out it, is not intended to be a normative specification. 
          Web Service Provider software often does not recognize the Media type 
          <em>application/xhtml+xml</em>. In that case the Web Author will have 
          to contact his or her Provider to try and convince them to adopt it as 
          the Media type to associate with XHTML Web Pages. If that doesn't work 
          -- and it may not -- then the Web Author will be faced with the task 
          of producing and loading up to the server a <strong>.htaccess</strong> 
          file that provides the association. Media types can also be established 
          via server side scripting.
        </p>
        <p>
          <span class="brown">Note that content-type specified in Meta tags is 
          only advisory - it does not affect the way the content is actually 
          served.</span>
        </p>
        <p>
          <a href="http://www.javascriptkit.com/howto/htaccess.shtml">Guide
          to .htaccess</a>
        </p>
        <p>
          Current XHTML/XML compliant browsers such as <em>Firefox, Mozilla, 
          Opera, Safari, et al.</em> will retrieve and render XHTML Web Pages 
          served as Media type <em>application/xhtml+xml</em> as intended
          - with full XML functionality.
        </p>
        <p>
          <a href="http://jp29.org/testx.html">Test/Demonstration page</a> 
          <span class="sp9">XHTML 1.0 (strict) Markup served with content 
          (MIME) type application/xhtml+xml</span>
        </p>
        <p>
          <strong>Serving XHTML 1.0 Web Pages as Media type <em>text/html</em>:</strong>
        </p>
        <p>
          <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/#guidelines">
          Appendix C of the XHTML 1.0 Recommendation</a> (HTML Compatibility 
          Guidelines) provides information for Web authors who wish to produce 
          XHTML Web Pages that will render in HTML specific user agents. 
          Such Web Pages must be served as Media type <em>text/html</em>
          -- <strong>which are HTML rather than XHTML pages</strong>. Again, 
          <em>W3C XHTML Media Types Note, 16 January 2009</em> provides 
          suggestions and guidance relating to the use of 
          <a href="http://www.w3.org/TR/xhtml-media-types/">
          <em>text/html</em></a> but is not intended to be a normative 
          specification. <strong>Practically all Web Pages with .htm or .html 
          extensions are being automatically served as <em>text/html</em> which 
          is the default Media type for most Web Service Provider software.</strong>
        </p>
        <p>
          <strong>Problems related to MSIE Browser rendering of XHTML Web Pages:</strong>
        </p>
        <p>
          <strong>MSIE Browsers will not retrieve and render XHTML served
          as Media type <em>application/xhtml+xml</em>
          correctly.</strong> MSIE 6.0 release 2900 and 7.0 will display
          such pages alright but will not render xml content.
          MSIE 6.0 release 2800 and earlier Browsers present a
          download screen -- selecting OPEN displays a plain,
          text only page (sans style sheet) and again will not
          render xml. <span class="sp8">IE6 Browsers render pages headed by 
          the XML prolog in Quirks mode - IE7 Browsers will skip the 
          prolog and render in Strict mode.</span>
        </p>
        <p>
          Microsoft's stated rationale for not recognizing XHTML
          Web Pages served with Media type
          <em>application/xhtml+xml</em> is set forth at:
        </p>
        <p>
          <a href="http://blogs.msdn.com/ie/archive/2005/09/15/467901.aspx">
          Microsoft MSIE 7.0 Blog</a>
        </p>
        <p>
          This is a dilemma for web authors and the W3C which has
          attempted to resolve this situation by embracing
          <strong>Content Negotiation</strong> -- usually via PHP
          on the server side as has been done with this page --
          in order to offer a choice of Media type
          <em>text/html</em> or <em>application/xhtml+xml</em>
          XHTML Web Pages to browsers so that they can render
          them according to their capabilities -- thus only XML
          compliant browsers will be served fully functional
          XHTML Web Pages.
        </p>
        <ul>
         <li>
          <a href="http://www.w3.org/2003/01/xhtml-mimetype/content-negotiation">
          XHTML Content Negotiation techniques</a>
         </li>
         <li>
          <a href="http://www.dyeager.org/articles/php_xhtml_mimetype.php">
          PHP, XHTML MIME type and Caching</a>
         </li>
         <li>
          <a href="https://developer.mozilla.org/En/Properly_Configuring_Server_MIME_Types">
          Properly Configuring Server MIME Types</a>
         </li>
         <li>
          <a href="http://juicystudio.com/article/content-negotiation.php">
          MIME Types and Content Negotiation</a>
         </li>
        </ul>          
        <p>
          <strong>Checking how pages are being served:</strong>
        </p>
        <p>
          The <a href="http://web-sniffer.net/">Web-Sniffer
          HTTP Request &amp; Response Header Viewer</a> can be
          employed to check how any Web Page is being served to various
          Browsers (specified via User Agent window). Following are
          depictions of how this page is being served to a 
          representative selection of typical Graphical Browsers:
        </p>
        <ul>
        <li>
          <a href="http://web-sniffer.net/?url=http%3A%2F%2Fjp29.org%2Ftest.php&amp;submit=Submit&amp;http=1.1&amp;gzip=yes&amp;type=GET&amp;uak=1">
          MS Internet Explorer 6.xx</a> - as text/html
        </li>
        <li>
          <a href="http://web-sniffer.net/?url=http%3A%2F%2Fjp29.org%2Ftest.php&amp;submit=Submit&amp;http=1.1&amp;gzip=yes&amp;type=GET&amp;uak=2">
          MS Internet Explorer 7.xx</a> - as text/html
        </li>
        <li>
          <a href="http://web-sniffer.net/?url=http%3A%2F%2Fjp29.org%2Ftest.php&amp;submit=Submit&amp;http=1.1&amp;gzip=yes&amp;type=GET&amp;uak=5">
          Firefox 2.xx</a> - as application/xhtml+xml
        </li>
        <li>
          <a href="http://web-sniffer.net/?url=http%3A%2F%2Fjp29.org%2Ftest.php&amp;submit=Submit&amp;http=1.1&amp;gzip=yes&amp;type=GET&amp;uak=4">
          Opera 9.xx</a> - as application/xhtml+xml
        </li>
        <li>
          <a href="http://web-sniffer.net/?url=http%3A%2F%2Fjp29.org%2Ftest.php&amp;submit=Submit&amp;http=1.1&amp;gzip=yes&amp;type=GET&amp;uak=6">
          Safari 3.xx</a> - as application/xhtml+xml
        </li>
       </ul>
        <p>
          <strong>XML compliant XHTML Checking tool (XML based
          rather than SGML based):</strong>
        </p>
        <ul>
         <li>
          <a href="http://schneegans.de/sv/">XML Schema Validator</a>
         </li>
        </ul>
        <p>
          <strong>Validation results for this page:</strong>
        </p>
        <p>
          <a href="http://validator.w3.org/check?verbose=1&amp;uri=http%3A//www.jp29.org/test.php">
          SGML Markup Validation</a> | <a href="http://schneegans.de/sv/?url=http%3A%2F%2Fjp29.org%2Ftest.php&amp;schema=%28Detect+automatically%29&amp;encoding=%28Detect+automatically%29&amp;htmlcomp=%28Detect+automatically%29">
          XML Schema Validation</a> | <a href="http://jigsaw.w3.org/css-validator/validator?uri=http://www.jp29.org/test.php">
          CSS Validation</a>
        </p>
        <p class="center">
          <a href="index.php">Go to the
          Web Authoring References and Resources page</a>
        </p>
        <p class="center">
          <a href="index.htm">Or go to my Web Sites &amp; Pages
          Portal</a>
        </p>
      </div>
    </div><!-- Start of StatCounter Code -->
    <script type="text/javascript">
var sc_project=4897746; 
var sc_invisible=1; 
var sc_partition=57; 
var sc_click_stat=1; 
var sc_security="2afbdb8b"; 
</script><script type="text/javascript" src="http://www.statcounter.com/counter/counter.js">
</script><noscript>
    <div class="statcounter">
      <a title="drupal hit counter" href="http://www.statcounter.com/drupal/"><img class="statcounter" src="http://c.statcounter.com/4897746/0/2afbdb8b/1/" alt="drupal hit counter" /></a>
    </div></noscript><!-- End of StatCounter Code -->
  </body>
</html>