#1160 new

Http header "Content-length" is not set for .ogv files

Reported by Grégory | October 13th, 2011 @ 04:07 PM

I’m building a HTML5 video player using the tag.
That player contains several sources including webm, ogv and mp4.
The problem is that play server is not sending HTTP "content-length" header for ".ogv" files and so, on client’s side, video player cannot detect video duration.
Content-length is sent correctly for .mp4 and .webm files.

Framework version: 1.2.3
Platform you're using: Linux Ubuntu 10.04 - OpenJDK 6 - Firefox 7

Reproduction steps:
1/ Build a basic HTML page with a video player and an ogv source :

     <video autoplay controls loop preload> 
    <source src="vid.ogv" /> 
    <source src="vid.mp4" /> 
    This content appears if the video tag or the codec is not supported.

(if needed, you can download pages and videos from here : javascript.training.free.fr/html5/exemples/multimedia/video.html )

2/ Serve that page on a play server

3/ view that page on Firefox browser (only Firefox reads ogv video) and use firebug to see http headers for that downloaded resource.
You’ll see that there is no content-length header for the ogv file.
The same method on Chrome (wich will use the mp4 source) shows a content-length header.


Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket