Web browsers often cache that file without checking for updates, even on
a forced reload, but there's a way to force that to happen. If you look
in the lunaserv.html file and search for where it loads lunaserv.yml,
there might already be something like "?reload=1" after it. The only
purpose for that is to force browsers to reload the yml file, just
change the 1 to anything else (2, a datestamp, whatever), and the
browser will then see it as a cache miss and pull the new yml file even
though the get parameter is otherwise meaningless.
--Nick
On 2020-05-21 09:35, 俊黄 wrote:
> Dear Nick,
> I updated the public/config/lunaserv.yml file with a new layer, and
> restarted passenger. However, the webpage didn't updated as I
> expected.
>
> Should I run something to update the webpage?
>
> Thanks!
> Jun
>
> --
> You received this message because you are subscribed to the Google
> Groups "Lunaserv" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to luna...@googlegroups.com.
Web browsers often cache that file without checking for updates, even on
a forced reload, but there's a way to force that to happen. If you look
in the lunaserv.html file and search for where it loads lunaserv.yml,
there might already be something like "?reload=1" after it. The only
purpose for that is to force browsers to reload the yml file, just
change the 1 to anything else (2, a datestamp, whatever), and the
browser will then see it as a cache miss and pull the new yml file even
though the get parameter is otherwise meaningless.
--Nick
On 2020-05-21 09:35, 俊黄 wrote:
> Dear Nick,
> I updated the public/config/lunaserv.yml file with a new layer, and
> restarted passenger. However, the webpage didn't updated as I
> expected.
>
> Should I run something to update the webpage?
>
> Thanks!
> Jun
>
> --
> You received this message because you are subscribed to the Google
> Groups "Lunaserv" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to luna...@googlegroups.com.