All good thanks folks. I think that was just feedvalidator being picky.
I still had an issue with iTunes though as they now require byte range support.
That required changing the headers in Azure storage, which does support them
but reports that it doesn’t if you’re on the old API.
Regards,
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
Can you browse to the static file store on azure and change it’s content type
in the properties dialog ?
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Low (??)
Sent: Wednesday, 1 March 2017 7:05 PM
To: ozDotNet
Subject:
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 |