Hi Samer,
I was finally able to test the caching changes in the 2.1.4 firmware, and unfortunately the problem persists. To test, I added a new program from the mobile interface, but was unable to see the new program on the browser until I reloaded the page.
Looking in Chrome’s debugger, I only see periodic calls to the jc and jo APIs, but only see a call to jp after reloading the page. I do, however, see the change to HTTP 1.1 and Cache-Control headers when the jp call is made. This suggests something else is going on as browser cached files typically appear in the debugger’s network timeline as such. This is likely something to do with the JavaScript handling this portion of the user interface, but I haven’t dug into it yet.