tags:

views:

435

answers:

5

What is the difference between .html and .xhtml extension? What is beneficial in .xhtml extension? and why we are not using .xhtml extension, is it just because of IE?

what about .xhtml extension with IE 8?

Is .xhtml supported in other browsers except IE ? if yes then what benefit we will get when all browser will support .xhtml extension. Will we leave to use .html on that day?

update:

Why we use xhtml doctype and save file as .html extension?

+6  A: 

If served over HTTP, the file extension has no meaning. The only information that matters it the Content-Type header field where the media type of the resource is specified.

But when served from a local filesystem, the media type is normally identified by the file extension.


Edit    I think the reason for why the extension .html is used even if it’s XHTML is because XHTML is HTML just with XML syntax and everyone is used to .html for HTML documents. (Although most XHTML documents are actually served as HTML as the media type text/html denotes HTML no matter what the document type declaration says.)

But again: extensions are not necessary when requested over HTTP. In HTTP the Content-Type header field tells what media type the resource should be interpreted with. So in theory you could use whatever extension you want or even use no extension at all (useful when content negotiation is used).

Gumbo
However, the extension usually has an effect on the Content-Type.
Ms2ger
@ms2ger: No, the file extension has absolutely no effect on Content-Type.
Gumbo
It "has an effect" in that servers often map extensions to Content-Types (e.g., via Apache's `AddType` directive or its `mime.types` file), but you're right that it doesn't change the file's content (that would indeed be quite odd).
Wevah
@Wevah: You’re right, but the server works on the filesystem. ;-)
Gumbo
+1  A: 

Nobody cares what the file is named, just what the MIME type it's been transferred with is.

Azeem.Butt
A: 

I think the xhtml extension is used for XHTML only, but it is rarely used, because the HTML-type you are using is defined in the DOCTYPE-element.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd"&gt;
Harmen
A: 

Browsers doesn't rely (just) on page extension, but in MIME content-type. This way you can, for instance, to create a PHP page which serves a JPG image.

Rubens Farias
A: 

IE (including IE8) is the only (significant) browser that doesn't support XHTML served as application/xhtml+xml (corresponds to the xht or xhtml extensions).

Will everyone move to XHTML when IE supports it? Probably not. XML isn't easy to get right, especially if you have to incorporate user-supplied data, such as blog comments. (Though that might be solved with (X)HTML5 <iframe sandbox> before IE starts playing along.) However, I don't have a crystal ball, so we'll just have to wait and see what happens.

Ms2ger