On Thu, Aug 06, 2015 at 07:26:34PM -0400, tunist wrote:

Hi there,

> i have now updated the serverfault question to include the nginx config
> files.

It looks like the question at http://serverfault.com/questions/710304/
has been changed so most current comments now look broken.

That's one downside of not using something like a mailing list where
the original context can be seen, even after the event.

Can I suggest you use a test server {} block, and strip that section of
your nginx.conf down to only what is essential to show the problem that
you are reporting?

(And post the smaller config here, so that people will be able to
copy-paste it into their test systems and reproduce exactly what you
are reporting.)

Right now, it looks to me as if your config says that a request for
/file.mp4 will be handled in "location / {}", which will just serve the
file /usr/local/nginx/html/file.mp4.

Is that what you expect? If so, you can remove all of the other location
{} blocks and have an effectively identical config for this request,
which will be much easier to analyse without getting distracted.

Also, you seem to be testing with "curl -I -r", and being surprised at
a HTTP 200 response. nginx returns HTTP 200 to HEAD requests for files.

Use something like "curl -i -r 5-10 http...file.mp4 | cat -v" to see
whether it sends a HTTP 206 with suitable headers. If it doesn't, then
you may have found an nginx problem.

(Right now, your example url gives me HTTP 302 and indicates that PHP
is involved somehow. It's hard to analyse things if they change silently.)

Good luck with it,

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx