ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Borisov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-11497) Web console: index.html is cached
Date Thu, 07 Mar 2019 03:13:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ilya Borisov reassigned IGNITE-11497:

    Assignee: Pavel Konstantinov  (was: Ilya Borisov)

> Web console: index.html is cached
> ---------------------------------
>                 Key: IGNITE-11497
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11497
>             Project: Ignite
>          Issue Type: Bug
>          Components: wizards
>            Reporter: Ilya Borisov
>            Assignee: Pavel Konstantinov
>            Priority: Major
> Some users, including [~pkonstantinov], reported cache-related issues for a long while.
According to [this article|https://blog.cronobo.com/2018/03/17/how-to-configure-caching-with-single-page-apps.html],
it might have to do with index.html caching, so let's disabled caching for this particular
> What to do:
> Disable index.html caching.
> Acceptance criteria:
> With "disable cache" option turned off in web inspector, index.html should always be
loaded from server. Here's a convoluted scenario:
> 1. Build docker image of web console
> 2. Open a tab (A), open web inspector on network tab, ensure caching is enabled, go to
web console.
> 3. Build the image again.
> 4. Open another tab (B), open web inspector on network tab, ensure caching is not disabled,
go to web console; index.html should not reported cache usage, js/css assets should have file
names different from same files in inspector of browser tab A.

This message was sent by Atlassian JIRA

View raw message