Bug 90732
| Summary: | [Soup] Wrong content-length reported for Youtube live streams | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Philippe Normand <pnormand> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bugs-noreply, mrobinson, svillar |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://youtube.com/live | ||
Philippe Normand
With patch from bug 90084 I can see the response.expectedContentLength() being a huge number, for a live stream (duration = infinite)... Instead 0 should be reported.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Philippe Normand
0 or some other value but not such huge number :)
Sergio Villar Senin
Actually I don't think there is any bug on wk as the server indeed specifies that content-length:
> GET /liveplay?ip=195.235.186.93&upn=WbwobTspM5k&sparams=algorithm%2Cburst%2Ccp%2Cfactor%2Cid%2Cip%2Cipbits%2Citag%2Cns%2Csource%2Cupn%2Cexpire&cp=U0hTSFFSTl9HTUNOM19JTFJJOi1KdEFrNzlWS3Fu&fexp=925500%2C910006%2C915507%2C907217%2C907335%2C921602%2C922600%2C919804%2C920704%2C924500%2C906831%2C924700%2C913547%2C920706%2C924402%2C907344%2C912706%2C902518&algorithm=throttle-factor&burst=40&ipbits=8&itag=34&sver=3&signature=3ADB9D6370C7DEFCE354E80C37EB10C7974F5C4E.20AFA3C69359FD0676079D79084874ACBF25006D&source=youtube&expire=1343170823&key=yt1&factor=1.25&ns=yt-live&id=dp29wce-mqI HTTP/1.1
> Soup-Debug-Timestamp: 1343147772
> Soup-Debug: SoupSessionAsync 1 (0xa3c840), SoupMessage 57 (0xbfec30), SoupSocket 39 (0x7f000400cc20)
> Host: v17.lscache1.c.youtube.com
> User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1+ (KHTML, like Gecko) Chromium/17.0.963.56 Chrome/17.0.963.56 Safari/537.1+
> icy-metadata: 1
> transferMode.dlna: Streaming
> Referer: http://www.youtube.com/user/CBCEgypt?feature=lb&v=dp29wce-mqI
> Accept: */*
> Accept-Encoding: gzip, deflate
> Connection: Keep-Alive
> Cookie: use_hitbox=d5c5516c3379125f43aa0d495d100d6ddAEAAAAw; VISITOR_INFO1_LIVE=-MuAl84ZGso; __utma=27069237.43384969.1343147772.1343147772.1343147772.1; __utmb=27069237.1.10.1343147772; __utmc=27069237; __utmz=27069237.1343147772.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PREF=f1=50000000&fv=0.0.0
< HTTP/1.1 1 Cancelled
< Soup-Debug-Timestamp: 1343147773
< Soup-Debug: SoupMessage 57 (0xbfec30)
< Last-Modified: Wed, 02 May 2007 10:26:10 GMT
< Content-Type: video/x-flv
< Date: Tue, 24 Jul 2012 16:36:13 GMT
< Expires: Tue, 24 Jul 2012 16:36:13 GMT
< Cache-Control: private, max-age=1
< Accept-Ranges: bytes
< Content-Length: 2147483646
< Connection: close
< X-Content-Type-Options: nosniff
< Server: gvls 2.0
PS: ignore the HTTP/1.1 1 Cancelled status code in the response, as it's how the WK MediaPlayer works for the gstreamer backend. It first cancels the original request and issues the exact same one to fully gain control over it.
Philippe Normand
So it's not the server returning a bogus Content-Length (-1)?
What should we do then?
Philippe Normand
Youtube live works now.