We have noticed that Smart Hub Preview sometimes retrieves the images with an incorrect path. This can be seen in the following web server access log:
62.178.121.60 - - [24/Aug/2022:07:17:41 +0200] “GET /orf/tvthek19/accelerator/accelerator.json HTTP/1.1” 200 4530 “-” “-”
…
62.178.121.60 - - [24/Aug/2022:07:17:52 +0200] “GET /orf/tvthek19/accelerator/se15219378.jpg HTTP/1.1” 200 25383 “-” “-”
62.178.121.60 - - [24/Aug/2022:07:17:52 +0200] “GET /orf/tvthek19/se15222662.jpg HTTP/1.1” 404 225 “-” “-”
62.178.121.60 - - [24/Aug/2022:07:17:52 +0200] “GET /orf/tvthek19/se15222557.jpg HTTP/1.1” 404 225 “-” “-”
62.178.121.60 - - [24/Aug/2022:07:17:52 +0200] “GET /orf/tvthek19/se15222612.jpg HTTP/1.1” 404 225 “-” “-”
62.178.121.60 - - [24/Aug/2022:07:17:52 +0200] “GET /orf/tvthek19/accelerator/se15222633.jpg HTTP/1.1” 404 237 “-” “-”
…
Here you can see that when retrieving the images, “accelerator” is sometimes missing from the path, although it is specified in accelerator.json.
For example, the image se15222662.jpg is sometimes called with and sometimes without accelerator in the path.
77.117.117.153 - - [24/Aug/2022:07:18:07 +0200] “GET /orf/tvthek19/accelerator/se15222662.jpg HTTP/1.1” 200 23759 “-” “-”
93.82.91.71 - - [24/Aug/2022:07:18:08 +0200] “GET /orf/tvthek19/accelerator/se15222662.jpg HTTP/1.1” 200 23759 “-” “-”
62.178.121.60 - - [24/Aug/2022:07:18:10 +0200] “GET /orf/tvthek19/se15222662.jpg HTTP/1.1” 404 225 “-” “-”
193.80.120.222 - - [24/Aug/2022:07:18:13 +0200] “GET /orf/tvthek19/accelerator/se15222662.jpg HTTP/1.1” 200 23759 “-” “-”
188.23.155.124 - - [24/Aug/2022:07:18:22 +0200] “GET /orf/tvthek19/accelerator/se15222662.jpg HTTP/1.1” 200 23759 “-” “-”
Question: Is there a known problem in this regard ?