Incorrect duration of some streamed audio files.

The client in my case is the one integrated in the native android player.
What I can see so far:
- not all files are affected.
- the file is not corrupted because readable with the link:
- curiously, the meta data duration which are contained in the first bytes of the audio file, is not correct when I partially download the file (usually the first 1000 KB) while the other meta datas are ok (title, album, art etc.).

Response headers for a file where the duration is correctly returned:

accept-ranges: bytes
    cache-control: max-age=60
    content-disposition: attachment; filename="Isaac Delusion - Midnight Sun.mp3"; filename*=UTF-8''Isaac%20Delusion%20-%20Midnight%20Sun.mp3
    content-security-policy: sandbox
    pragma: public
    referrer-policy: no-referrer
    vary: Origin, Accept-Encoding
    x-content-security-policy: sandbox
    x-content-type-options: nosniff
    x-robots-tag: noindex, nofollow, noimageindex
    x-server-response-time: 46
    x-webkit-csp: sandbox
    content-type: application/json
    accept-encoding: identity,gzip
    date: Sat, 12 Feb 2022 11:30:52 GMT
    server: envoy
    strict-transport-security: max-age=31536000; includeSubDomains; preload
    x-robots-tag: noindex, nofollow, noimageindex
    content-encoding: gzip
    x-dropbox-response-origin: far_remote
    x-dropbox-request-id: a76b8827cea24632ad411939dea04550

Response headers for a file where the returned duration is not correct:

accept-ranges: bytes
    cache-control: max-age=60
    content-disposition: attachment; filename="Pixies - Dig for Fire.mp3"; filename*=UTF-8''Pixies%20-%20Dig%20for%20Fire.mp3
    content-security-policy: sandbox
    pragma: public
    referrer-policy: no-referrer
    vary: Origin, Accept-Encoding
    x-content-security-policy: sandbox
    x-content-type-options: nosniff
    x-robots-tag: noindex, nofollow, noimageindex
    x-server-response-time: 47
    x-webkit-csp: sandbox
    content-type: application/json
    accept-encoding: identity,gzip
    date: Sat, 12 Feb 2022 11:28:20 GMT
    server: envoy
    strict-transport-security: max-age=31536000; includeSubDomains; preload
    x-robots-tag: noindex, nofollow, noimageindex
    content-encoding: gzip
    x-dropbox-response-origin: far_remote
    x-dropbox-request-id: f63eef26b69d49c18ebb96ca9e1d4ffc

In both cases I don't have a "content-length" header?.

I noticed  content-type: application/json  and not audio/mpeg why?
To get this headers in response I used okhttp client.

In fact, this problem appeared recently.

same result if I force the protocol with HTTP/2 with:

public static OkHttpClient getHttp2Client(){
        ConnectionPool connectionPool = new ConnectionPool();
        return new OkHttpClient.Builder()
                .followRedirects(true)
                .protocols(Arrays.asList(Protocol.HTTP_2,Protocol.HTTP_1_1))
                .retryOnConnectionFailure(true)
                .connectionPool(connectionPool)
                .build();
    }

"you should update your client/code to support "Transfer-Encoding: chunked" 

 Does this mean that I have to add "Transfer-Encoding: chunked" as a header to my request?