2019-05-31, 11:46
Kodi 18.2 on Windows 10.
I have a media source in Videos/Files whose path is like
[This directory contains: none] and [Exclude selected folder from scans] are checked in [Set content] for the media source, but Kodi seems to scan all the subfolders nonetheless (I can see a lot of GET and HEAD requests in my http server log) as soon as I click the media source root.
Most are HEAD requests for items like poster.jpg, poster.png, fanart.jpg, fanart.png, banner.jpg, banner.png, thumb.jpg, thumb.png, movie.tbn, folder.jpg (there are no such files on the server).
To reach the server I have to go through an HTTP proxy that requires NTLM authentication, therefore I have Proxifier intercepting network calls.
When I browse the source I can see in the Proxifier log that Kodi opens a TCP connection for every single request.
This seems a very poor optimization choice, expecially for HTTPS (SSL overhead is not negligible).
Why not using a few HTTP persistent connections?
HTTP persistent connection
I have a media source in Videos/Files whose path is like
https://hostname.dom:443/resource/[This directory contains: none] and [Exclude selected folder from scans] are checked in [Set content] for the media source, but Kodi seems to scan all the subfolders nonetheless (I can see a lot of GET and HEAD requests in my http server log) as soon as I click the media source root.
Most are HEAD requests for items like poster.jpg, poster.png, fanart.jpg, fanart.png, banner.jpg, banner.png, thumb.jpg, thumb.png, movie.tbn, folder.jpg (there are no such files on the server).
To reach the server I have to go through an HTTP proxy that requires NTLM authentication, therefore I have Proxifier intercepting network calls.
When I browse the source I can see in the Proxifier log that Kodi opens a TCP connection for every single request.
This seems a very poor optimization choice, expecially for HTTPS (SSL overhead is not negligible).
Why not using a few HTTP persistent connections?
HTTP persistent connection