Hi Roger, just to update you on the situation.
I did some more digging into the problem im having and it was suggested that i tried re-submitting the feed to the store.
On doing so i got the error message that my hosting does not have byte-range support which it seems a lot of people are having problems with. Having read further it seems apple introduced these changes around the time my podcast stopped updating which seems to tie into how the issue started.
So i created a test feed with one episode and a link to a media file from a working podcast and still it would not submit, i was getting the 'We have difficulty reading this feed. Connection Reset error'
Luckily i have another hosting provider so i uploaded the exact same test feed and the feed got accepted.
So i have come to the conclusion that my host does not have byte-range support but also it seems this is stopping it reading the actual .xml file as well as the .mp3 content which from reading other posts should not happen.
So im in the process of uploading the latest episode to my host that has byte-range support enabled and im going to update my current feed with one episode and a link to the .mp3 file on the server with byte-range support enabled and im hoping fingers crossed the feed updates.
Obviously i can set up a new feed on the server with byte-range support enabled but if my current feed fails to update at all im concerned i will never be able to update the feed again and therefore never be able to add the feed URL redirect code in order to keep my subscribers.
Thought id share this with you as it may help you in helping others having similar problems.
Richard Pitts
