Forum Discussion

DGPT's avatar
DGPT
Visitor
9 years ago

URL Feed Not Validated: Expecting text/xml but rcvd text/plain

I am trying to upload my Feed URL for the first time. I have done the following:


  • Created JSON file (in Google Docs and then exporting as a .txt file)

  • Tested it in the Schema Validator

  • Uploaded it to my AWS as a .txt file

  • Linked to it in my Roku Developer page


My Feed URL is here:
https://s3.amazonaws.com/assets.dgpt.co ... ONFile.txt

I get the following error: 
The feed URL(s) could not be validated.
  • The server returned an unsupported content type. Was expecting 'application/rss+xml', 'text/xml', 'application/xml' or 'application/json' but received 'text/plain'.

    Any help is greatly appreciated. My guess is that I need to define a file type, but I do not know how to do this (or where).
  • 8 Replies

    • Try uploading it as a ".json" file, since that's what it is.
    • I have changed the extension to .json and tried uploading it and get the same "URL Feed not validated" error message.

      The new file is located at http://dgprotour.weebly.com/uploads/5/1/7/2/51727149/dgptjsonfile.json

      Unfortunately, I'm still getting the following error: 
      The feed URL(s) could not be validated.
    • The server returned an unsupported content type. Was expecting 'application/rss+xml', 'text/xml', 'application/xml' or 'application/json' but received 'text/plain'.
    • Your ".txt" file on AWS is served with a Content-Type of "text/plain", which is what I'd expect from a ".txt" file. I'm not familiar with AWS, but I would try changing the extension to ".json" and see if AWS serves it up with a Content-Type of "application/json".

      Your ".json" file on Weebly is served with a Content-Type of "application/octet-stream". I'm not sure how (or if) you could change that on Weebly. In any case, it's a violation of Weebly's Terms of Service to host files that weren't created with the Weebly editor.
    • "belltown" wrote:
       I'm not familiar with AWS, but I would try changing the extension to ".json" and see if AWS serves it up with a Content-Type of "application/json".

      I have JSON files on S3. They won't work unless I change the properties/metadata to txt/rtf. There is no application/json option.   I'm using getToString() to snag it.
    • Thank you, the JSON and XML file give me the same reply when trying to upload to AWS:


      “DGPT-ROKU-FEED.xml” has failed to upload. Sorry, this file type is not permitted for security reasons.

      On Weebly, I uploaded the file successfully and now get the following error:

      For MRSS feeds a video type must be provided.

      Does the conversion to XML mean that I am now using MRSS? If so, there are apparently different parameters/types that need to be defined?
      My guess is that I somehow went from a JSON feed to an MRSS feed with the JSON-->XML conversion.

      Does anyone know of a sample MRSS feed that I can utilize to replicate my new file from?