fuelbox

bump

Hi Hugh. Not trying to be a nag ?? but was wondering if you’ve had any time to give this some thought?
Thanks a bunch.

Hi again Hugh. Well, I finally have more information about the byte-range request error. Apologies in advance for the long post.

Short version:
Our paths to the actual mp3 files in the XML are getting redirected. Is this caused by the plugin or WordPress itself?

Long version:
Godaddy ran multiple tests and they said they confirmed that their server supports byte-range requests. So… I asked iTunes support for help and they responded with this:

You can test byte-range requests by looking in the grey box on the right side here:
https://castfeedvalidator.com/?url=https://feeds.feedburner.com/VictoryVida
When iTunes accesses the file:
https://victoryatl.com/victoryvida/podcast-download/4151/yo-creo-en-dios-mi-sanador.mp3
it is redirected to:
https://victoryatl.com/victoryvida/files/2015/10/vida_2015_1018_yo_creo_dios_mi_sanador.mp3
Which does not respond correctly with:
HTTP 206 Partial Content
“Accepts Ranges: Bytes”

Provide the info below to GoDaddy and request they reconfirm.
==== Provide this information to GoDaddy ====
curl -H Range:bytes=50-60 -I -L https://victoryatl.com/victoryvida/files/2015/10/vida_2015_1018_yo_creo_dios_mi_sanador.mp3
HTTP/1.1 200 OK
Date: Tue, 19 Jan 2016 19:20:35 GMT
Server: Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4
X-Powered-By: PHP/5.4.33
ETag: “acfd1382d062d2188d0807a096fe7ef6”
Expires: Fri, 22 Mar 2019 05:07:15 GMT
Content-Length: 46386821
Last-Modified: Thu, 22 Oct 2015 12:47:53 GMT
Content-Type: audio/mpeg

=== Example of correct response ===
curl -H Range:bytes=50-60 -I -L https://traffic.libsyn.com/mvclc/2016-01-17_AM_Time_is_a_Treasure.mp3
HTTP/1.1 302 Found
Date: Tue, 19 Jan 2016 20:30:37 GMT
Server: Apache
Location: https://ec.libsyn.com/p/b/a/f/baf03ef280f31882/2016-01-17_AM_Time_is_a_Treasure.mp3?d13a76d516d9dec20c3d276ce028ed5089ab1ce3dae902ea1d06cd8435d2c15c04b2&c_id=10713110
X-Libsyn-Host: traffic4.libsyn.com
Vary: Accept-Encoding
Connection: close
Content-Type: text/html
HTTP/1.1 206 Partial Content
Accept-Ranges: bytes
Cache-Control: max-age=2592000
Content-Range: bytes 50-60/15828241
Content-Type: audio/mpeg
Date: Tue, 19 Jan 2016 20:30:37 GMT
Etag: “569adde3-f18511”
Expires: Fri, 19 Feb 2016 00:07:06 GMT
Last-Modified: Sun, 17 Jan 2016 00:18:43 GMT
Server: ECAcc (sjc/4EA8)
Via: 1.1 varnish
X-Cache: HIT
X-Varnish: 1619265824
Content-Length: 11

I forwarded this new info to a tech at Godaddy who responded with this:

Thank you for providing more information on this issue. Using this specific example and command I was able to verify that the server settings are properly working with byte-ranges, however anything going through your WordPress application is not. As a specific example, you can use the exact same referenced MP3 file as a direct link on the server and it works without issue:

$ curl -H Range:bytes=50-60 -I -L https://victoryatl.com/wp-content/blogs.dir/19/files/2015/10/vida_2015_1018_yo_creo_dios_mi_sanador.mp3
HTTP/1.1 206 Partial Content
Date: Thu, 21 Jan 2016 01:20:14 GMT
Server: Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4
Last-Modified: Thu, 22 Oct 2015 12:47:53 GMT
ETag: “43a2227-2c3ce85-522b0e74682a0”
Accept-Ranges: bytes
Content-Length: 11
Content-Range: bytes 50-60/46386821
Content-Type: audio/mpeg

The only difference made versus Apple’s example is to use the direct address to the file:
https://victoryatl.com/wp-content/blogs.dir/19/files/2015/10/vida_2015_1018_yo_creo_dios_mi_sanador.mp3
vs
https://victoryatl.com/victoryvida/files/2015/10/vida_2015_1018_yo_creo_dios_mi_sanador.mp3

As this issue is being caused within your WordPress issue, you will need to either find an alternative method of linking or uploading or review this issue with your WordPress developers.

All of this to say that the problem seems to be a redirected path. Not really sure why it’s tagged as a byte-range request error.

Thanks for any info you can provide.

Thanks Hugh. I’ll go back to the host and re-hash this and keep my fingers crossed.

Hi Hugh. Just a follow up to see if you ever found any solutions to the byte-range request issue. We’re having that problem with iTunes and have confirmed that the server is configured correctly. We are using a MultiSite installation (version 4.3.1). Thanks in advance for any advice.

i was having the same problem, but i finally found it. if you click on “Screen Options” at the top right, you’ll be able to check Post Revisions.
i wish this was selected by default, but oh well.

steve