Guy,

    I've found that IE5 does not always listen to the specified content-type
header, rather attempts to figure the document type using a set of rules.
For example a document such as:
garbage <?xml version="1.0" ?>
will get read as XML rather than say text/plain

    There are a bunch of other situations but suffice to say that IE5 does
not depend on nor always listen to the Content-Type: header to arrive at the
document type (I do wish it would).

Jonathan


>Hi Jonathan.
>
>It works in practice too, as I did this for an intranet app prototype. I
>haven't got direct access to the files anymore, but I'll try and get them
>e-mailed to me to make 100% sure (only 95% sure :) of what I'm saying as I
>could be mistaken.
>
>Cheers
>
>    Guy

> err. theoretically this would work... in practice IE5 is confused and
>looks
>> only for a file extension .xml leading to the hack
>>
>> xxx.asp?whatever=yyy&dummy=x.xml
>>
>>
>>
>> > Hi.
>> >
>> > You might try setting...
>> >
>> > Response.ContentType = 'text/xml';
>> >
>> > ...so that the mimetype of the returned file is appropriate, in which
>case
>> > IE5 will accept ASP files OK.
>> >
>> > Cheers
>> >     Guy



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list