byte-range requests

'Byre range requests' are the method used by iPhones to stream podcasts, consisting of requesting sections of the file at a time rather than the whole thing in one go. Some servers don't handle this, with the result that those podcasts don't work properly on iPhones, leading to complaints. Hence it's mandatory if you want to submit your podcast to the iTunes Store.

How you actually enable it isn't a podcasting question and is outside my experience, so I can't advise on it. I can only suggest that you try forums handling servers, particularly whatever type you have - Linux, Apache, or whatever. If you can do so without swearing you would be more likely to attract a sympathetic response.

I can't diagnose that readout, but if you care to post the URL of one of your media files (not the feed) I can check in Terminal and see whether it looks as if your server is behaving as required.

The Terminal test does indicate that byte range requests are supported. I've highlighted the relevant two lines below.

curl -I -r 200-300 http://giombg.giombg.eu/mp3_32/9records/9REC009-01@32.mp3

HTTP/1.1 206 Partial Content

Date: Thu, 03 Mar 2016 22:56:09 GMT

Server: Apache/2.2.15 (CentOS)

Last-Modified: Tue, 01 Mar 2016 08:52:06 GMT

ETag: "1a80775-1a37a6-52cf8e13df980"

Accept-Ranges: bytes

Content-Length: 101

Content-Range: bytes 200-300/1718182

Connection: close

Content-Type: audio/mpeg

I don't know why they are failing it given that curl and CastFeedValidator pass it. Have you tried using the contact form podba.se provide (by clicking the query sign at bottom right of the page) and asking if they can clarify their diagnosis?

Otherwise I can only suggest contacting iTunes Support and asking them for clarification. Goto https://itunespartner.apple.com/en/podcasts/overview and click the 'Contact Us' link at the bottom of the page.