Hi Spartanicus
the reason I didn't post the url is that it is located on a "part-time"
server which is not always running, I'll try and keep it up at least for
today, the url is included in the out put bellow, neither firefox or moz
have any problems with this, but I will upload to a reomte server to see
if it makes any difference
GET / HTTP/1.1[CRLF]
Host: os2.no-ip.info[CRLF]
Connection: close[CRLF]
Accept-Encoding: gzip[CRLF]
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5[CRLF]
Accept-Language: sv,en-us;q=0.7,en;q=0.3[CRLF]
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[CRLF]
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.7.12)
Gecko/20050922 Web-Sniffer/1.0.22[CRLF]
Referer:
http://web-sniffer.net/[CRLF]
[CRLF]
it also gave it a responce header
HTTP Status Code: HTTP/1.1 200 OK
Date: Sat, 15 Oct 2005 09:30:46 GMT CRLF
Server: Apache/2.0.53 (OS/2) PHP/4.3.10 CRLF
Last-Modified: Fri, 14 Oct 2005 20:58:36 GMT CRLF
ETag: "0-791-1f01f700" CRLF
Accept-Ranges: bytes CRLF
Content-Length: 1937 CRLF
Connection: close CRLF
Content-Type: application/xhtml+xml
I cant see anything here to indicate a problem
regards
Adrian Suri
adrian suri <as**************@tele2.se> wrote:
Re file names and IE
Don't prefix a subject of a new post with "Re".
when using the extension *.xhtml internet explorer refuses to load them
and simple gives the opeption to open or save, apache2 seems to be
passing through ok, mozzila loads them fine, and yes validates with
w3.org going through the same server
I'm going to assume that you didn't tell us this because you thought we
would like to know (we don't), but that you are in fact looking for the
reason and possibly a solution.
The noted IE behaviour typically occurs when the content is served with
the http header Content-Type: application/xhtml+xml
Had you posted the url we would have been able to check the mime type.
If you don't have a way to check the mime type you can use a web service
like http://web-sniffer.net/
If that is the reason then your web server is probably configured to
send out this mime type for files ending in ".xhtml". Change the server
configuration if you don't want that, or change the file "extension" to
htm or html.