Bug #5007
No channel Picons (imagecache error 400) on 4.3.x
0%
Description
I want to use Picons in kodi htsp client.
Install tvh 4.3-1159~gc64482d.
Configure satellite TV. Everything is work.
I create folder and set it in Configuration - General - Base - Picon path: file:///home/hts/picons
Set permissions: chown -R hts: /home/hts/picons
In /home/hts/picons folder has icons format: 1_0_16_191_4_70_1680000_0_0_0.png that corresponds to (example) Configuration - Channel / EPG - Channels - User Icon column: picon://1_0_16_191_4_70_1680000_0_0_0.png
In webui, in "Electronic Program Guide" tab in event details i can see channel picon therefore tvheadend can see picons folder.
After starting Kodi with htsp client in tv section i scroll channels and picons does not appear.
In log i see:
мар 15 21:58:18 tvhtest1604 tvheadend6898: http: 127.0.0.1: HTTP/1.1 HEAD (2) /imagecache/588 -- 400
мар 15 21:58:18 tvhtest1604 tvheadend6898: http: 127.0.0.1: HTTP/1.1 GET (1) /imagecache/588 -- 400
мар 15 21:58:18 tvhtest1604 tvheadend6898: http: 127.0.0.1: HTTP/1.1 HEAD (2) /imagecache/417 -- 400
мар 15 21:58:18 tvhtest1604 tvheadend6898: http: 127.0.0.1: HTTP/1.1 GET (1) /imagecache/417 -- 400
After reinstall stable tvh 4.2.5.x and start over configure with the same /home/hts/picons folder picons in htsp client are show correctly.
History
Updated by Jaroslav Kysela over 6 years ago
Try to set 'digest+plain' HTTP authentication in the tvh configuration.
Updated by Ivan Mara over 6 years ago
I set: Configuration - Base - HTTP Server settings - Authentication type: Both plain and digest and picons appeared in kodi! But in "Digest" authentication type there is no picons in kodi. Is it Bug ?
Updated by Jaroslav Kysela over 6 years ago
- Status changed from New to Rejected
You may ask to implement the digest authentication in pvr.hts (Kodi) - https://github.com/kodi-pvr/pvr.hts/issues . It's not TVH issue (the digest is more secure than the plain authentication which sends the password unencrypted).
Updated by Jaroslav Kysela over 6 years ago
Just a minor update - the latest TVH sends correct 401 Unauthorized code to the client in this case (when the authentication method is disallowed).