Cannot direct play from Emby via .strm file

Streaming & Network
1

My Emby server’s media library consists of .strm files, each containing a signed HTTPS URL. When accessed, this URL returns a 302 redirect to the actual media resource URL.

When I connect Infuse to my Emby server and attempt to play content, the /Items/14603/PlaybackInfo?UserId=xxx endpoint returns a response like this(ignored other fields):
{“MediaSources”: [{
“Container”: “mp4”,
“IsRemote”: true,
“Path”: “https://example.com/moviexxx.mp4?sign=xxx”,
“Protocol”: “Http”,
“SupportsDirectPlay”: true,
“SupportsDirectStream”: true,
“SupportsProbing”: true,
“SupportsTranscoding”: true,
}]}

This includes SupportsDirectPlay: true, and the Path field contains the signed URL directly.

According to my understanding and the Emby’s developer document, Direct Play mode has the highest priority and the client should directly access the Path URL to play the content itself.
However, in practice, Infuse still calls the /Videos/14603/stream endpoint and uses direct stream, which consumes my Emby server’s bandwidth.

My question is: Is this the intended behavior, or is there a setting I need to configure to enable true direct play from Emby?

Code: T4GKK