Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


Apple podcasts must be served from a byte-range enabled server. This allows users to stream episodes. More info here:

I have Lamp stack Apache/PHP/Mysql. When I test with wget or Curl (specifying byte-range) and request static files from the server byte-range works - Apache is doing its thing.

When I request dynamic content the request is handed to PHP, which then hands the entire file to Apache, which then completes the request delivering the entire file. THis is expected behaviour.


I was curios to what others have implemented to get round this.

At first I considered Apache rewrites to point to the physical file on the server. However due to some app requirements this is not possible in this situation.

Placing Nginx at the top of the stack and configuring it to handle byte-range requests. Nginx > Apache > PHP.

Updating the PHP code to handle byte range requests.

Thanks for reading. I'm interested to the best way to resolve this.

THanks again.

share|improve this question
just run test with x-sendfile and seems like a reasonable solution to this. – hokeycokey May 27 '12 at 19:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.