{"action":"opened","issue":{"url":"https://api.github.com/repos/Geta/SEO.Sitemaps/issues/73","repository_url":"https://api.github.com/repos/Geta/SEO.Sitemaps","labels_url":"https://api.github.com/repos/Geta/SEO.Sitemaps/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/Geta/SEO.Sitemaps/issues/73/comments","events_url":"https://api.github.com/repos/Geta/SEO.Sitemaps/issues/73/events","html_url":"https://github.com/Geta/SEO.Sitemaps/issues/73","id":319424317,"number":73,"title":"The sitemap isn't validated","user":{"login":"haspe85","id":38903566,"avatar_url":"https://avatars2.githubusercontent.com/u/38903566?v=4","gravatar_id":"","url":"https://api.github.com/users/haspe85","html_url":"https://github.com/haspe85","followers_url":"https://api.github.com/users/haspe85/followers","following_url":"https://api.github.com/users/haspe85/following{/other_user}","gists_url":"https://api.github.com/users/haspe85/gists{/gist_id}","starred_url":"https://api.github.com/users/haspe85/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/haspe85/subscriptions","organizations_url":"https://api.github.com/users/haspe85/orgs","repos_url":"https://api.github.com/users/haspe85/repos","events_url":"https://api.github.com/users/haspe85/events{/privacy}","received_events_url":"https://api.github.com/users/haspe85/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-02T06:27:06Z","updated_at":"2018-05-02T06:27:06Z","closed_at":null,"author_association":"NONE","body":"Hi!\r\n\r\nI have a sitemap.xml from this addon and its created and I can visit it correctly. \r\n\r\nBut when running a validate check with http://validator.w3.org/ it gives an error: \r\nSorry! This document cannot be checked.\r\n\r\nMissing \"charset\" attribute for \"text/xml\" document.\r\n\r\nThe HTTP Content-Type header (text/xml) sent by your web server (Microsoft-IIS/8.5) did not contain a \"charset\" parameter, but the Content-Type was one of the XML text/* sub-types.\r\n\r\nThe relevant specification (RFC 3023) specifies a strong default of \"us-ascii\" for such documents so we will use this value regardless of any encoding you may have indicated elsewhere.\r\n\r\nIf you would like to use a different encoding, you should arrange to have your server send this new encoding information.\r\n\r\nKind regards\r\n/ Henric"}}
{"actor":{"display_login":"haspe85"}}