Enhancement to http response header when accessing hubitat local files

I have been working on building a cheap wireless speaker that streams mp3 files stored locally on Hubitat (like the cached speech files). When requesting the file from Apache, the response headers look like this:
image
image

Here are the response headers from Hubitat for the same file:
image
image

The lack of a "content-length" header in the 2nd group makes the mp3 player think that this is a stream, not a file, and it expects the data to continue past the end, throwing an error and a repeat of the last several bytes of the audio file.

Is it possible to include the content-length in all the response headers instead of just the first one and not set the transfer encoding to chunked?

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.