Invalid Content-Range header for prefixed range request

When sending a prefixed range request like:

GET /sound.wav HTTP/1.1
Host: localhost:7673
Connection: keep-alive
Cache-Control: max-age=0
Accept-Encoding: identity;q=1, *;q=0
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.93 Safari/537.36
Accept: /
Range: bytes=0-

Undertow responds with:

HTTP/1.1 206 Partial Content
Connection: keep-alive
Cache-Control: no-cache
Last-Modified: Fri, 27 Jun 2014 16:25:36 GMT
Content-Range: 0--1/72464
Content-Length: 72464
Content-Type: audio/x-wav
Date: Wed, 22 Jul 2015 13:44:07 GMT

The Content-Range is invalid. It should be 0-72463/72464. The internal "-1 == unbounded" is leaked into the response.

The failure is readily visible if you try to serve an audio file to Chrome.