4 p.m.
We seem to have many questions each release related to non-working
things due to stale browser cache. Usually it's due to changes in admin
console, but it may be even worse if we ever change something in CSS/JS
of login or account mgmt, as those are available for end users.
I wonder if we can somehow improve this? One possible solution is to
attach the redundant parameter with version to the cached resources.
Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
upgrade to next version will force browser to reload the resource.
The problem is longer (and not so nice) URLs and also some refactoring
needed. For freemarker templates, we can add version parameter at
runtime. However for admin console HTML pages, we would need to add
version somehow at compile time though.
There is also possibility to attach hash instead of version (Juca
mentioned this to me some time ago), but not sure if it's big difference.
Any better ideas? Or should we rather just keep it as it is?
Marek
4:07 p.m.
What about have something that intercept requests to disable browser caching ? A servlet
filter or something ...
----- Original Message -----
From: "Marek Posolda" <mposolda(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, February 3, 2015 8:00:07 PM
Subject: [keycloak-dev] Improve browser caching?
We seem to have many questions each release related to non-working
things due to stale browser cache. Usually it's due to changes in admin
console, but it may be even worse if we ever change something in CSS/JS
of login or account mgmt, as those are available for end users.
I wonder if we can somehow improve this? One possible solution is to
attach the redundant parameter with version to the cached resources.
Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
upgrade to next version will force browser to reload the resource.
The problem is longer (and not so nice) URLs and also some refactoring
needed. For freemarker templates, we can add version parameter at
runtime. However for admin console HTML pages, we would need to add
version somehow at compile time though.
There is also possibility to attach hash instead of version (Juca
mentioned this to me some time ago), but not sure if it's big difference.
Any better ideas? Or should we rather just keep it as it is?
Marek
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
1:55 a.m.
----- Original Message -----
From: "Pedro Igor Silva" <psilva(a)redhat.com>
To: "Marek Posolda" <mposolda(a)redhat.com>
Cc: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, 3 February, 2015 11:07:11 PM
Subject: Re: [keycloak-dev] Improve browser caching?
What about have something that intercept requests to disable browser caching
? A servlet filter or something ...
We actively enable browsing caching to increase performance, so not sure why we would want
a filter to disable it?
----- Original Message -----
From: "Marek Posolda" <mposolda(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, February 3, 2015 8:00:07 PM
Subject: [keycloak-dev] Improve browser caching?
We seem to have many questions each release related to non-working
things due to stale browser cache. Usually it's due to changes in admin
console, but it may be even worse if we ever change something in CSS/JS
of login or account mgmt, as those are available for end users.
I wonder if we can somehow improve this? One possible solution is to
attach the redundant parameter with version to the cached resources.
Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
upgrade to next version will force browser to reload the resource.
The problem is longer (and not so nice) URLs and also some refactoring
needed. For freemarker templates, we can add version parameter at
runtime. However for admin console HTML pages, we would need to add
version somehow at compile time though.
There is also possibility to attach hash instead of version (Juca
mentioned this to me some time ago), but not sure if it's big difference.
Any better ideas? Or should we rather just keep it as it is?
Marek
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
6:18 a.m.
----- Original Message -----
From: "Stian Thorgersen" <stian(a)redhat.com>
To: "Pedro Igor Silva" <psilva(a)redhat.com>
Cc: "Marek Posolda" <mposolda(a)redhat.com>, keycloak-dev(a)lists.jboss.org
Sent: Wednesday, February 4, 2015 5:55:40 AM
Subject: Re: [keycloak-dev] Improve browser caching?
----- Original Message -----
> From: "Pedro Igor Silva" <psilva(a)redhat.com>
> To: "Marek Posolda" <mposolda(a)redhat.com>
> Cc: keycloak-dev(a)lists.jboss.org
> Sent: Tuesday, 3 February, 2015 11:07:11 PM
> Subject: Re: [keycloak-dev] Improve browser caching?
>
> What about have something that intercept requests to disable browser
> caching
> ? A servlet filter or something ...
We actively enable browsing caching to increase performance, so not sure why
we would want a filter to disable it?
Actually, manage caching. So you can control how http caching is set in responses. If you
want to disable, you just change a config. Or if you want to set a default expiration time
for pages or specific resources.
>
> ----- Original Message -----
> From: "Marek Posolda" <mposolda(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Tuesday, February 3, 2015 8:00:07 PM
> Subject: [keycloak-dev] Improve browser caching?
>
> We seem to have many questions each release related to non-working
> things due to stale browser cache. Usually it's due to changes in admin
> console, but it may be even worse if we ever change something in CSS/JS
> of login or account mgmt, as those are available for end users.
>
> I wonder if we can somehow improve this? One possible solution is to
> attach the redundant parameter with version to the cached resources.
> Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
> upgrade to next version will force browser to reload the resource.
>
> The problem is longer (and not so nice) URLs and also some refactoring
> needed. For freemarker templates, we can add version parameter at
> runtime. However for admin console HTML pages, we would need to add
> version somehow at compile time though.
>
> There is also possibility to attach hash instead of version (Juca
> mentioned this to me some time ago), but not sure if it's big difference.
>
> Any better ideas? Or should we rather just keep it as it is?
>
> Marek
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
6:22 a.m.
----- Original Message -----
From: "Pedro Igor Silva" <psilva(a)redhat.com>
To: "Stian Thorgersen" <stian(a)redhat.com>
Cc: "Marek Posolda" <mposolda(a)redhat.com>, keycloak-dev(a)lists.jboss.org
Sent: Wednesday, 4 February, 2015 1:18:17 PM
Subject: Re: [keycloak-dev] Improve browser caching?
----- Original Message -----
> From: "Stian Thorgersen" <stian(a)redhat.com>
> To: "Pedro Igor Silva" <psilva(a)redhat.com>
> Cc: "Marek Posolda" <mposolda(a)redhat.com>,
keycloak-dev(a)lists.jboss.org
> Sent: Wednesday, February 4, 2015 5:55:40 AM
> Subject: Re: [keycloak-dev] Improve browser caching?
>
>
>
> ----- Original Message -----
> > From: "Pedro Igor Silva" <psilva(a)redhat.com>
> > To: "Marek Posolda" <mposolda(a)redhat.com>
> > Cc: keycloak-dev(a)lists.jboss.org
> > Sent: Tuesday, 3 February, 2015 11:07:11 PM
> > Subject: Re: [keycloak-dev] Improve browser caching?
> >
> > What about have something that intercept requests to disable browser
> > caching
> > ? A servlet filter or something ...
>
> We actively enable browsing caching to increase performance, so not sure
> why
> we would want a filter to disable it?
Actually, manage caching. So you can control how http caching is set in
responses. If you want to disable, you just change a config. Or if you want
to set a default expiration time for pages or specific resources.
We already manage caching though. We set max-age to allow browsers to cache resources that
are not dynamic. We could use etags, but that still requires a request to the server. So
the only decent solution I can think of is making sure we have a unique url, which we can
do by adding a version/hash or something.
>
> >
> > ----- Original Message -----
> > From: "Marek Posolda" <mposolda(a)redhat.com>
> > To: keycloak-dev(a)lists.jboss.org
> > Sent: Tuesday, February 3, 2015 8:00:07 PM
> > Subject: [keycloak-dev] Improve browser caching?
> >
> > We seem to have many questions each release related to non-working
> > things due to stale browser cache. Usually it's due to changes in admin
> > console, but it may be even worse if we ever change something in CSS/JS
> > of login or account mgmt, as those are available for end users.
> >
> > I wonder if we can somehow improve this? One possible solution is to
> > attach the redundant parameter with version to the cached resources.
> > Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
> > upgrade to next version will force browser to reload the resource.
> >
> > The problem is longer (and not so nice) URLs and also some refactoring
> > needed. For freemarker templates, we can add version parameter at
> > runtime. However for admin console HTML pages, we would need to add
> > version somehow at compile time though.
> >
> > There is also possibility to attach hash instead of version (Juca
> > mentioned this to me some time ago), but not sure if it's big difference.
> >
> > Any better ideas? Or should we rather just keep it as it is?
> >
> > Marek
> > _______________________________________________
> > keycloak-dev mailing list
> > keycloak-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-dev
> > _______________________________________________
> > keycloak-dev mailing list
> > keycloak-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-dev
> >
>
6:23 a.m.
Or just use KC behind an Apache server and forget about managing that in KC :)
----- Original Message -----
From: "Stian Thorgersen" <stian(a)redhat.com>
To: "Pedro Igor Silva" <psilva(a)redhat.com>
Cc: "Marek Posolda" <mposolda(a)redhat.com>, keycloak-dev(a)lists.jboss.org
Sent: Wednesday, February 4, 2015 5:55:40 AM
Subject: Re: [keycloak-dev] Improve browser caching?
----- Original Message -----
From: "Pedro Igor Silva" <psilva(a)redhat.com>
To: "Marek Posolda" <mposolda(a)redhat.com>
Cc: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, 3 February, 2015 11:07:11 PM
Subject: Re: [keycloak-dev] Improve browser caching?
What about have something that intercept requests to disable browser caching
? A servlet filter or something ...
We actively enable browsing caching to increase performance, so not sure why we would want
a filter to disable it?
----- Original Message -----
From: "Marek Posolda" <mposolda(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, February 3, 2015 8:00:07 PM
Subject: [keycloak-dev] Improve browser caching?
We seem to have many questions each release related to non-working
things due to stale browser cache. Usually it's due to changes in admin
console, but it may be even worse if we ever change something in CSS/JS
of login or account mgmt, as those are available for end users.
I wonder if we can somehow improve this? One possible solution is to
attach the redundant parameter with version to the cached resources.
Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
upgrade to next version will force browser to reload the resource.
The problem is longer (and not so nice) URLs and also some refactoring
needed. For freemarker templates, we can add version parameter at
runtime. However for admin console HTML pages, we would need to add
version somehow at compile time though.
There is also possibility to attach hash instead of version (Juca
mentioned this to me some time ago), but not sure if it's big difference.
Any better ideas? Or should we rather just keep it as it is?
Marek
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
1:55 a.m.
https://issues.jboss.org/browse/KEYCLOAK-1017 ;)
I was thinking it would be cleaner to add it to the URL of theme resources.
/auth/theme/.../<VERSION>/stylesheet.css
This works better for relative URLs.
Not sure I like using the release version, we could have a short hash or just an
incrementing number.
----- Original Message -----
From: "Marek Posolda" <mposolda(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, 3 February, 2015 11:00:07 PM
Subject: [keycloak-dev] Improve browser caching?
We seem to have many questions each release related to non-working
things due to stale browser cache. Usually it's due to changes in admin
console, but it may be even worse if we ever change something in CSS/JS
of login or account mgmt, as those are available for end users.
I wonder if we can somehow improve this? One possible solution is to
attach the redundant parameter with version to the cached resources.
Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
upgrade to next version will force browser to reload the resource.
The problem is longer (and not so nice) URLs and also some refactoring
needed. For freemarker templates, we can add version parameter at
runtime. However for admin console HTML pages, we would need to add
version somehow at compile time though.
There is also possibility to attach hash instead of version (Juca
mentioned this to me some time ago), but not sure if it's big difference.
Any better ideas? Or should we rather just keep it as it is?
Marek
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
2:11 a.m.
On 4.2.2015 08:55, Stian Thorgersen wrote:
https://issues.jboss.org/browse/KEYCLOAK-1017 ;)
I was thinking it would be cleaner to add it to the URL of theme resources.
/auth/theme/.../<VERSION>/stylesheet.css
This works better for relative URLs.
+1
Not sure I like using the release version, we could have a short hash or just an
incrementing number.
Sure, we can use whatever of this. Hash might have an advantage
that can
be generated at compile time though. So it's even better for us during
development as version is still "1.2.0.Beta1-SNAPSHOT" but hash will
always change (not sure about KeycloakServer, which is usually executed
directly from IDE and bypasses maven, but maybe there is some solution
for this too).
Marek
----- Original Message -----
> From: "Marek Posolda" <mposolda(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Tuesday, 3 February, 2015 11:00:07 PM
> Subject: [keycloak-dev] Improve browser caching?
>
> We seem to have many questions each release related to non-working
> things due to stale browser cache. Usually it's due to changes in admin
> console, but it may be even worse if we ever change something in CSS/JS
> of login or account mgmt, as those are available for end users.
>
> I wonder if we can somehow improve this? One possible solution is to
> attach the redundant parameter with version to the cached resources.
> Something like: "/auth/theme/.../stylesheet.css?v=1.1.0.Final", so
> upgrade to next version will force browser to reload the resource.
>
> The problem is longer (and not so nice) URLs and also some refactoring
> needed. For freemarker templates, we can add version parameter at
> runtime. However for admin console HTML pages, we would need to add
> version somehow at compile time though.
>
> There is also possibility to attach hash instead of version (Juca
> mentioned this to me some time ago), but not sure if it's big difference.
>
> Any better ideas? Or should we rather just keep it as it is?
>
> Marek
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
4077
days inactive
4078
days old
7 comments
3 participants
participants (3)
-
Marek Posolda -
Pedro Igor Silva -
Stian Thorgersen