Apache Byte-Range Request Compatibility Tests Provide Inconsistent Results

dswimr615

• December 28, 2017 14:23

Hello, A client of ours is trying to get their site compatible (Site #1) to byte-range requests as Apple requires it for some of its software. When performing the following test on their website: curl -H Range:bytes=16- -I domain.org We get the following: HTTP/1.1 200 OK Date: Thu, 28 Dec 2017 20:10:10 GMT Server: Apache X-Powered-By: PHP/5.3.29 Content-Type: text/html As you can see, a 200 request is being returned when a 206 Partial Content is expected (and is what we want). On Site #2 located on the same server with the same VirtualHost content and no .htaccess or php.ini or CageFS differences, we get the following with the same test: HTTP/1.1 206 Partial Content Date: Thu, 28 Dec 2017 19:49:57 GMT Server: Apache Last-Modified: Wed, 20 Mar 2013 21:12:28 GMT Accept-Ranges: bytes Content-Length: 10881 Content-Range: bytes 16-10896/10897 Content-Type: text/html The above is what we want with Site #1. What is the variable that needs to be changed?

• 

  cPanelMichael

  • December 28, 2017 20:10

  Hello, Are you running the cURL command from the cPanel server's command line? If so, verify the cPanel server is routing the website to the correct IP address. For instance, if you temporarily add an "IP domain.org" entry in the /etc/hosts file, do you see the same results? Thank you.

  0
• 

  dswimr615

  • December 29, 2017 15:54

  Hello, Are you running the cURL command from the cPanel server's command line? If so, verify the cPanel server is routing the website to the correct IP address. For instance, if you temporarily add an "IP domain.org" entry in the /etc/hosts file, do you see the same results? Thank you.

  
  Hey Michael, That's not far off from what I expected, as the problem site does indeed have a dedicated IP (but other sites with a dedi IP work properly with this test). I added a hosts entry for the website, however, as well as ran the curl command from the server the site is on but still no luck. HTTP/1.1 200 OK Date: Fri, 29 Dec 2017 16:39:23 GMT Server: Apache X-Powered-By: PHP/5.3.29 Content-Type: text/html I just checked something and it appears to be consistent-- could the issue possibly be the TLD? I'm going through testing sites that don't end in .com, and all of them are returning similar incorrect results as above.

  0
• 

  cPanelMichael

  • December 30, 2017 18:00

  Hello, Could you open a support ticket using the link in my signature so we can take a closer look and rule out any server configuration issues? Thank you.

  0

Please sign in to leave a comment.