iTunes error - Bad http result code: 403

[SteveWebb]

If this has been addressed elsewhere, I'm sorry for posing this question here. I did try searching and did not find that this problem has shown up on the forum.

I am attempting to submit some category podcasts, but iTunes returns the following message: "We had difficulty reading this feed. Bad http result code: 403"

Any idea what I can do to get this through? The feeds do validate at feedvalidator.org.

Thanks for your help!

[angelo]

Anythign can cause this, poorly executed firewall,  mod_proxy in web server, mod_security, not including the / at the end of the URL, etc..

Please reply with the URL to the feed so we can take a look.

[SteveWebb]

Thanks Angelo. Here's an example: http://lifespringmedia.com/category/in-touch-with-gods-character/feed/

[angelo]

First glance, you have your file size length set to 1 in some cases, most likely PowerPress was unable to detect the file size for what ever reason. Looking at your media file URLs and they appear to be hosted at Amazon
S3. You are aware that S3 is a storage system, you need to configure CloudFront to host files from S3 right?

I would re-Verify the URLs for the media files that are reporting file size of 1 byte. I would also search this forum for the iTunes feed submission problem for an explanation how to submit your podcast feed to avoid that problem/

[SteveWebb]

Thanks, Angelo. I'll work on these and see if this resolves the problem.

[SteveWebb]

Angelo, I provisioned my S3 for the CDN option and replaced all the links that pointed to Mevio's servers. All the links in the feed are now good feeds.

I am still getting the same error from iTunes.

In your last post, you suggested I "search this forum for the iTunes feed submission problem for an explanation how to submit your podcast feed to avoid that problem/"

I did search the forum for the 403 error and didn't find much. Can you be a bit more specific on what you think I should search for?

Thanks.

[angelo]

http://forum.blubrry.com/index.php/topic,3455.msg9321.html#msg9321 itunes feed timeout.

[SteveWebb]

Thanks. I'll give that a look. I appreciate your help!

[SteveWebb]

Actually the forum link you reference addresses a time out error. That's not my issue, and the fix given in that link does not help me at all.

I have been trying to submit my feed in the manner described in that post.

Any other ideas?

[angelo]

Contact Apple.

[angelo]

When you get a resolution with Apple, please reply on this forum so we know what's up.

[SteveWebb]

Turns out the problem was caused by a WordPress security plugin: BulletProof Security.

Perhaps, Angelo, you could take a look at this plugin to see if there is a way you could make PowerPress and BulletProof play well together? Having had some pretty severe hacking problems in the past, I hate to leave BulletProof behind.

[angelo]

Security at the php level, e.g. plugin is usually a little too late in the security process. You would be better served fin.ding a host or server administrator who knows how to setup a firewall, configure mod_security, and knows how to setup file permissions and limit what folders can and can't run cgi/php.

I will add this plugin to the list of plugins to investigate compatibility.

[SteveWebb]

Actually, what BulletProof does is create some pretty sophisticated (in my *totally not an expert* view) .htaccess files that limit what outsiders can do to your site. I'll be interested to know what your findings are once you get a chance to look at it.

[angelo]

.htaccess files are folder specific, I am sure it creates stuff that's ideal as far as Apache security is concerned, but above/beyond that, a secure site would not allow most of the rules to work in .htaccess files in the first place. The thinking is that if a plugin could write .htaccess files, than so could any other process that could run by the web server, which in-itself is a security problem. If this security plugin walks you through setting the file permissions to these .htaccess files after it generates them then that's better, but still not ideal.

I understand though that economics plays a big part in being able to afford a full time administrator or paying a hefty dime for web hosting that has security measures in place. I'll look into the plugin conflict at some point soon.