{"push_id":2319019557,"size":1,"distinct_size":1,"ref":"refs/heads/streams-unify-disableRange-contentLength","head":"ad06979cca677be6d68fdbb7a4765a65b1abaeb7","before":"00d191fb49540737fe7bd6fcaad929f316d2ccb8","commits":[{"sha":"ad06979cca677be6d68fdbb7a4765a65b1abaeb7","author":{"name":"Jonas Jenwald","email":"bbd857ad5277dd198029c09f6d4b8824489d8ede@gmail.com"},"message":"Attempt to unify the `disableRange`/`contentLength` handling in the various network streams\n\nFirst of all, note how in both `fetch_stream.js` and `node_stream.js` we always overwrite the `this._contentLength` property even when the response headers doesn't actually contain any (valid) length information. This could thus result in the `length` parameter, as passed to the network stream, being completely ignored despite having no better information available.\nSecondly, in `node_stream.js` the `this._isRangeSupported` property wasn't always updated correctly based on the response headers.","distinct":true,"url":"https://api.github.com/repos/Snuffleupagus/pdf.js/commits/ad06979cca677be6d68fdbb7a4765a65b1abaeb7"}]}
{"actor":{"display_login":"Snuffleupagus"}}