http-content-range

I'm streaming audio files from a Node.js Express server with Content-Range headers plus no caching headers. This works ok in latest Safari instead, but it does not in Chrome. While when streaming the full audio file with HTTP 200 , my headers were { 'Content-Length': 4724126, 'Content-Type': 'audio/mpeg', 'Access-Control-Allow-Origin': '*', 'Access-Control-Allow-Methods': 'POST, GET, OPTIONS', 'Access-Control-Allow-Headers': 'POST, GET, OPTIONS', Expires: 0, Pragma: 'no-cache', 'Cache-Control': 'no-cache, no-store, must-revalidate' } and it works on both Chrome and Safari <audio> tag. When

My problem was that I couldn´t upload files bigger than 4MB so I used the createuploadsession according to createuploadsession I successfully get the uploadUrl value from the createuploadsession response. Now I try to make a PUT request with this code var file = 'C:\\files\\box.zip' fs.readFile(file, function read(e, f) { request.put({ url: 'https://api.onedrive.com/rup/545d583xxxxxxxxxxxxxxxxxxxxxxxxx', headers: { 'Content-Type': mime.lookup(file), 'Content-Length': f.length, 'Content-Range': 'bytes ' + f.length } }, function(er, re, bo) { console.log('#324324', bo); }); }); But I will get as

I am working on an existing Silverlight file uploader that breaks files into multiple chunks and transmits the file using multiple HTTP requests. Currently, it sends the start and total byte information on the querystring, but as learning exercise, I'd like to use a more standards-based approach. I've previously used the HTTP Content-Range header when implementing an endpoint that serves content. Is this header also appropriate to use when posting content from a client to the server? Yes. RFC 2616 (HTTP 1.1), Section 14 begins by stating: For entity-header fields, both sender and recipient

This may be a Servlets question or an HTML5 question, depending on what the solution turns out to be... :) I've got a (Tomcat) Servlet serving up short clips of audio which are then picked up in an HTML5 audio element. The audio correctly plays, but on some browsers only once (so that attempting to "rewind" or replay the audio does not then work). I suspect that this is because my Servlet is not reporting that it supports range requests: I notice that given a static audio file on the same server, Apache adds the HTTP "range-unit" response header, and replaying the file then works in such cases