Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: "Podcast cover art must be at least 600 X 600 pixel JPG or PNG, in RGB color space, and hosted on a server that allows HTTP head requests"

I keep getting this error message. I'm not sure which of the issues I'm encountering. I think this is the only thing preventing my podcast feed from being submitted to iTunes. I tested out the HTTP head request at web-sniffer.net and below was the result I got. The link to my artwork is https://archive.org/download/EdgeSteelWithWhitemedRes/edge%20steel%20with%20whit e%20%28med%20res%29.png . Can anyone help me?


HTTP Request Header

Connect to 207.241.224.2 on port 443 ... ok GET /download/EdgeSteelWithWhitemedRes/edge%20steel%20with%20white%20%28med%20res%29.png HTTP/1.1[CRLF] Host: archive.org[CRLF] Connection: close[CRLF] User-Agent: Web-sniffer/1.0.46 (+http://web-sniffer.net/)[CRLF] Accept-Charset: ISO-8859-1,UTF-8;q=0.7,*;q=0.7[CRLF] Cache-Control: no-cache[CRLF] Accept-Language: de,en;q=0.7,en-us;q=0.3[CRLF] Referer: http://web-sniffer.net/[CRLF] [CRLF]

HTTP Response Header

Status: HTTP/1.1 302 Moved Temporarily
Server: nginx/1.1.19
Date: Sun, 02 Feb 2014 03:13:17 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
X-Powered-By: PHP/5.3.10-1ubuntu3.2
Accept-Ranges: bytes
Location: https://ia600801.us.archive.org/28/items/EdgeSteelWithWhitemedRes/edge steel with white (med res).png

Posted on

Reply
Question marked as Solved
Answer:
Answer:

jmseidler wrote:


Here's the latest link to my image.

http://imgur.com/p96IFqQ

In fact the relevant tag reads


<itunes:image href="https://lh4.googleusercontent.com/-6M4p2M10N6U/Uuhm3-zwrTI/AAAAAAAAACc/7xn8-d1-i Bc/w140-h140-p/edge%2Bsteel%2B%2528high%2Bres%2529.png" />


The URL begins with https (encrypted connection) and this is likely to throw the Store.

Posted on

Page content loaded

Feb 1, 2014 11:44 PM in response to jmseidler In response to jmseidler

The image appears to be OK though it contains an alpha channel and I don't know whether iTunes is thrown by that or not. You could try re-saving it as a JPG or as a PNG without the alpha channel and see what happens.


I don't know anything about 'head requests', though I notice that there is a 302 in place.

Feb 1, 2014 11:44 PM

Reply Helpful

Feb 2, 2014 2:26 AM in response to Roger Wilmut1 In response to Roger Wilmut1

I did a bit of research: this is what I understand from it. Most requests to a server use GET which retrieves the entire document. It looks as if that was what you were using above.


A HEAD request is simply intended to retrieve the header of the page or file, not the entire thing. The purpose of this is to use the metadata to check whether the file is available, and, for example, its modification date. This means that if you have a cached copy you can check whether it's been updated without having to download the entire file, thussaving time and bandwidth.


All servers must support GET or you wouldn't be able to access the file at all, but the implication is that some don't support HEAD, just as some don't support byte range requests (requesting part of the file at a time, as used by iPhones). So I suppose all you can do is to ask the people running your server whether it supports HEAD. If it doesn't, you will presumably have to find another server.


I hope this is an accurate summary, as I say it's outside my previous experience and was gleaned by looking at a few web pages, principally


http://net.tutsplus.com/tutorials/other/http-headers-for-dummies/


302 by the way is a temporary redirect, meaning that the next time you check the server you will check the original URL, whereas a 301 redirects permanently (in theory).


Looking again at your URL, you are using https - this is likely to cause problems and you should preface the URL with http. You should also remove the spaces from the file name - presumably the feed (which you haven't linked to so I can't check it) has substituted the code %20 for each space (otherwise it wouldn't work at all) but it's bad practice - spaces are not allowed in a URL. You could replace each space with an underscore.


If your media file URLs begin with https you should use http instead. https (secured connection) won't work in the Store.

Feb 2, 2014 2:26 AM

Reply Helpful

Feb 2, 2014 8:17 PM in response to Roger Wilmut1 In response to Roger Wilmut1

It's kind of funny. I can subscribe to the podcast manually in iTunes by entering the URL, but I can't submit it to the store. Even when subscribing manually, the podcast artwork shows up fine. I've tried several other image hosts today, but I'm still getting the same error message. All the links are below in case you need them.


Here's the latest link to my image.

http://imgur.com/p96IFqQ


Here's the link to my feed.

http://feeds.feedburner.com/theedgedayton


Here's the link to my blog.

http://theedgedayton.blogspot.com/


Here's the link to my sound file.

http://archive.org/download/Enemies_201401/Enemies.mp3

Feb 2, 2014 8:17 PM

Reply Helpful

Feb 2, 2014 10:40 PM in response to Roger Wilmut1 In response to Roger Wilmut1

I am getting this same error when I attempt to submit a new podcast. I've submitted over 30 podcasts using FeedforAll and have never had this issue before. I'm using the same server I've always used. Has something changed on iTunes. I did some reading and found contradictory instructions. The error message says that the cover image needs to be 600 x 600 pixels The specs on the iTunes site says 1400 x 1400 which would be insanely huge. I know I've never created an image file for iTunes that was that large and all of my current images are still working.
Where can one go to get a definitive answer to this issue?
Here is my feed:
http://www.bamradionetwork.com/feeds/satchat.xml

Here is the link to the image file:
http://www.bamradionetwork.com/feeds/satchatitunes.png

Feb 2, 2014 10:40 PM

Reply Helpful

Feb 2, 2014 10:55 PM in response to Roger Wilmut1 In response to Roger Wilmut1

I just took a known good feed that has been accepted by iTunes and is currently listed. I changed the name, placed the feed on another server and submitted it to iTunes and a new feed. I'm getting the same error. It looks like something is wrong on the iTunes site.


How do we contact admin for this?

Feb 2, 2014 10:55 PM

Reply Helpful
Question marked as Solved

Feb 2, 2014 11:43 PM in response to jmseidler In response to jmseidler

jmseidler wrote:


Here's the latest link to my image.

http://imgur.com/p96IFqQ

In fact the relevant tag reads


<itunes:image href="https://lh4.googleusercontent.com/-6M4p2M10N6U/Uuhm3-zwrTI/AAAAAAAAACc/7xn8-d1-i Bc/w140-h140-p/edge%2Bsteel%2B%2528high%2Bres%2529.png" />


The URL begins with https (encrypted connection) and this is likely to throw the Store.

Feb 2, 2014 11:43 PM

Reply Helpful

Feb 2, 2014 11:47 PM in response to Jack Street In response to Jack Street

Jack Street wrote:


I am getting this same error when I attempt to submit a new podcast.

Your image is 310 x 310 and that may be the issue. 1400 x 1400 is specified if you want a chance for your podcast to be 'featured'; 600 x 600 has been quite common but I don't know whether they are now making 1400 x 1400 mandatory.


It's preferable if you start a new thread when you have a question; if the OP comes back we will have interleaved answers and it can get quite confusing.

Feb 2, 2014 11:47 PM

Reply Helpful

Feb 2, 2014 11:56 PM in response to Roger Wilmut1 In response to Roger Wilmut1

Thanks for the reply Roger.


I'm assuming you haven't seen my follow up note.


I took a known good feed that has been accepted by iTunes and is currently listed. I changed the name, placed the feed on another server and submitted it to iTunes as a new feed. I'm getting the same error. It looks like something is wrong on the iTunes site.


How do we contact admin for this?

Feb 2, 2014 11:56 PM

Reply Helpful

Feb 3, 2014 7:51 AM in response to jmseidler In response to jmseidler

UPDATE: I created a new cover image using 1400 x1400 pixels in the RGB colorspace using Photoshop. I resubmitted and it worked. Apparently they now insisting on the 1400 x1400 image. I plan to update all of my old images to ensure that they will still display properly on itunes going forward.

Feb 3, 2014 7:51 AM

Reply Helpful

Feb 3, 2014 6:50 PM in response to Roger Wilmut1 In response to Roger Wilmut1

Hello, I'm having the same problem. I even resized my image and redid the feed. It still says the covert art needs to be 1400x1400. This is the image I have http://i.imgur.com/smOoTf4.jpg and my RSS Feed is http://soundsofsbla.wordpress.com/tag/podcasts/feed I just want to get sent in for review so I can speed up the process but this cover art thing is a HASSLE!!! Please help me, I've been trying to get this issue resolved forever!

Feb 3, 2014 6:50 PM

Reply Helpful

Feb 3, 2014 11:33 PM in response to darksayian101 In response to darksayian101

Your image won't appear because your feed is not properly constructed as a podcast feed. It has an 'enclosure' tag correctly and so will work, but it lacks the 'iTunes declaration' in the second line -


<rss xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" version="2.0">


and has no 'itunes:...' tags such as subtitle and summary, including 'itunes:image' which is necessary for your image to show.


You have constructed your feed in WordPress and presumably there is a setting there to make the feed iTunes-compliant but I can't advise on details. There is a plugin called PodPress which may help.

Feb 3, 2014 11:33 PM

Reply Helpful
User profile for user: jmseidler

Question: "Podcast cover art must be at least 600 X 600 pixel JPG or PNG, in RGB color space, and hosted on a server that allows HTTP head requests"