We’re using proxy_store on the edge server for replicating requested
mp4
files and some of our users reported that some of the videos are half
sized
and therefore they are unable to stream whole video file on their end
(coming from the edge server). On digging into the access_logs of nginx,
i
found the 500 internal server errors for 10~20 videos and on checking
the
size of 500 error videos it was half of the size compare to the mirrored
video files on the origin. Please check the following error of the
culprit
video link :-
203.124.62.213 - - [18/Sep/2014:15:13:58 +0500] “GET
/files/videos/2014/09/12/1410536044adf1b-360.mp4?start=729 HTTP/1.1” 500
588 “http://lw3.files.com/files/videos/2014/09/12/” “Mozilla/4.0
(compatible; MSIE 8.0; Windows NT 6.0)”
I’d like to inform that the issue is coming for 40% of the videos.
Do you have the mp4 module enabled at the origin? If so then you have
partial mp4
downloaded from there and stored locally. Note proxy_pass without URI
passes
client URIs to the origin keeping the arguments (including start).
This issue is fixed, now i am getting another issue. Whenever user
requests
for new file which is not yet downloaded on the edge server, user gets
the
403 forbidden error on browser and on refreshing the browser, the same
video started to stream as well as download. Why the proxy_store is
showing
403 error on first time ?
On Thu, Sep 18, 2014 at 6:45 PM, shahzaib shahzaib [email protected]
I have seen your directives and I am not nginx expert but there was
something like “try” for connections to a proxy server that will first
try one direction and if not able to download from there use the other
one.
Take a peak here:
You can define two backends: store and proxy.
First try store and then proxy.
(I do hope I am right about the assumption)