Greg, This discussion:-
http://stackoverflow.com/questions/4832357/whats-the-difference-between-text-xml-vs-application-xml-for-webservice-respons Seems to indicate that it's more a client issue. Your server response header is setting the content type to text/xml but not the charset but and though that should be good enough for modern clients, that read the xml document encoding and honour it, some might still use the default us-ascii. It may be possible that the feed validator is is just being "picky". IIS should let you set the charset on that content type so the feed validates. https://forums.iis.net/t/1155439.aspx -- noonie On 1 March 2017 at 19:04, Greg Low (罗格雷格博士) <g...@greglow.com> wrote: > But that still leaves the question on how to change that. It's just > serving up a static xml file. How is the content type for that specified? > And more importantly, where? > > Regards, > > Greg > > Dr Greg Low > 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 > fax > SQL Down Under | Web: www.sqldownunder.com > > ------------------------------ > *From:* ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> on > behalf of Bill McCarthy <bill.mccarthy.li...@live.com.au> > *Sent:* Wednesday, March 1, 2017 5:32:06 PM > > *To:* ozDotNet > *Subject:* RE: XML files served by Azure Websites > > > Just looked at feedvalidator.org . Look at the help link: > > http://www.feedvalidator.org/docs/warning/EncodingMismatch.html > > > > your site is serving up response content type: text/xml > > > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-bounces@ > ozdotnet.com] *On Behalf Of *Greg Low (??????) > *Sent:* Wednesday, 1 March 2017 4:55 PM > *To:* ozDotNet <ozdotnet@ozdotnet.com> > *Subject:* Re: XML files served by Azure Websites > > > > Yes I did think BOM was on UTF-16. Either way, issue seems to be the > header from the site. No idea where to set it. I'm suspecting that the lack > of a value probably sends this as a default. Can't find ASCII mentioned > anywhere in project files. > > Regards, > > Greg > > Dr Greg Low > 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 > fax > SQL Down Under | Web: www.sqldownunder.com > > > ------------------------------ > > *From:* ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> on > behalf of Bill McCarthy <bill.mccarthy.li...@live.com.au> > *Sent:* Wednesday, March 1, 2017 3:05:00 PM > *To:* ozDotNet > *Subject:* RE: XML files served by Azure Websites > > > > Thought it was the other way around and that BOM was unnecessary for > utf-8. > > To me Greg’s problem looks like the server is sending a response block > saying the content type is asci, then send an xml file which is utf-8. > Would have to do old school spit out bytes to test as I doubt any text > editor would permit the file to be saved as ascii as it would be invalid > ascii file > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-bounces@ > ozdotnet.com <ozdotnet-boun...@ozdotnet.com>] *On Behalf Of *David Connors > *Sent:* Wednesday, 1 March 2017 2:55 PM > *To:* ozDotNet <ozdotnet@ozdotnet.com> > *Subject:* Re: XML files served by Azure Websites > > > > On Wed, 1 Mar 2017 at 13:41 Bill McCarthy <bill.mccarthy.li...@live.com.au> > wrote: > > The file itself is utf-8, or unicode due to special characters in it, eg > Lòpez > > So problem is not with the file. > > > > No, a UTF-8 stream is defined as such by a byte order marker at the start > of the stream. You can have UTF-8 files composed entirely of ASCII > characters. > > > > -- > > David Connors > da...@connors.com | @davidconnors | LinkedIn | +61 417 189 363 > <+61%20417%20189%20363> > > -- > > David Connors > da...@connors.com | @davidconnors | LinkedIn | +61 417 189 363 >
