https://bugzilla.wikimedia.org/show_bug.cgi?id=43477
--- Comment #5 from Mark Bergsma <[email protected]> --- (In reply to comment #3) > (In reply to comment #2) > > > however it also does not play the videos opening video urls directly. > > > http://upload.wikimedia.org/wikipedia/commons/thumb/6/68/ > > Spawning_Pocillopora_meandrina_-_pone.0050847.s002.ogv/ > > Spawning_Pocillopora_meandrina_-_pone.0050847.s002.ogv.360p.webm > > For me this works with two limitations: I have to pause and re-start the > playing and I only hear the sound and do not see any video (because they are > served as audio/webm, which let opera use the audio html element to show it; > reported in bug 43476). > > It seems, that you're right about the squid/range thing. I had a look at the > request headers and compared them to what is happening in Firefox: > > In Firefox the request looks relatively normal: The request for the webm file > is a range request: "Range: bytes=0-". The answer is "HTTP/1.0 206 Partial > Content" with "Content-Range: bytes 0-2408692/2408693" (this is for > File:0GLOBO.ogv on commons). > > With Opera this looks a bit strange: At first there is a request which is > nearly the same as the firefox request. But immediately after the first > request > (Range: bytes=0-), a second request is sent to the server (Range: > bytes=2400193-2408692; If-Range: 0a7703c116193f8057eb330718428963). So the > end > of the file is requested (maybe to get the duration like for ogg videos, but > normally this isn't needed for webm), but until this second request I didn't > see any answer from the server - how does Opera know the content length and > the > ETag (for If-Range)? At least there is only one answer to this request and > it's > not a 206 but a 200 (although both request are range requests). It seems to > me, > that Opera thinks the file which is sent altogether is the answer to the last > range request. When trying to reload this video directly in opera, always the > second range request is made (the end of the file) - that's why it didn't > even > work directly in Opera after trying to watch it using the mediawiki player. > > The question is: Why does the servers answer with 200 instead of 206 to a > range > request from opera but with 206 to a range request from firefox? Is it > because > of the If-Range thing? I just did a bit of testing, but haven't been able to reproduce this yet. Could you please do another packet capture and post the full request and response, so I can exactly replicate the request? What I did notice so far is that Varnish seems to ignore If-Range completely. A quick grep through the source indicates that it's not evaluating that header at all. -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
