: What are the causes of a 416 Error? One of my visitors from my website informed me that every so often (quite rarely actually), when trying to visit my website, he gets a 416 Error: Requested

@Dunderdale272

This looks like a duplicate question:
stackoverflow.com/questions/5891431/416-requested-range-not-satisfiable
check the explanation here:
www.addedbytes.com/for-beginners/http-status-codes/
But basically, check the error log for the 416 error [I know you said you checked - it should be there unless you are including a resource from another server] that should tell you what file - then make sure it is getting cached correctly [or not cached at all]

-sean

UPDATE:

what you can do with APC, is disable caching of certyain files by using the apc.filters setting in your php.ini [or apc.inc or however you are including the apc config] If you can figure out which file[s] are throwing the 416 error, you can start by configuring APC to not cache them. Sounds like a reasonable start to me.

AAAACtually, come to think of it, if you can find the file throwing the error, you can use APC to 1. see if it is cached & 2. check on the file size that APC thinks it is then 3. check the actual size on disk. Check out this link: devzone.zend.com/article/12618 [the official APC docs kinda suck]

Vote Up Vote Down

@Nimeshi995

That error means that some client sends a request to your server which specifies a range of bytes which is not serveable due to some reason.

This can happen with something like this example:


You have an image with physical size 1000 bytes
Your Server specifies the wrong content length e.g. 1500
The client sends a request to get 0 - 1500 bytes from your server
Your server sends a 416 because the image has only 1000bytes

Vote Up Vote Down