https://htmx.org logo
Powered by
# htmx-general
  • p
    <meta name="htmx-config" content='{"historyCacheSize": 0, "historyRefreshOnHistoryMiss": true}'>
  • p
    same result
  • p
    hmm might not even be an issue with hx-boost
  • p
    hx-get + hx-push-url has same problem
  • p
    it just restores the target, and doesn't reload the whole page
  • p
    so issue is using hx-push-url or hx-boost: even though it pushes new URL, page will not reload from that URL when reloading browser session.
  • p
    "historyRefreshOnHistoryMiss" doesn't make any difference
  • p
    confirmed on two browsers & two devices
  • m
    it's a browser cache issue almost certainly
  • m
    are you seeing the request hit your server?
  • p
    yes but I'm seeing it affect multiple browsers/devices
  • p
    so what I think is happening is that when you have hx-push-url + an hx-get, the result of that fetch is what is being restored by the browser
  • p
    even though it's an html fragment
  • m
    Yes, that's my guess too. On the restoration the browser cache is taking the last fragment returned by that URL.
  • p
    and it doesn't appear to be hitting the server
  • m
    So we'd need to set the No Cache header for it
  • m
  • p
    yeah
  • p
    a pain
  • p
    as otherwise hx-push-url or hx-boost is broken
  • p
    I had it set in but that makes no difference
  • m
    huh
  • p
    <meta name="Cache-Control" content="no-cache">
  • p
    so will need to set as http header
  • m
    i wonder if there is a way to say "this is the canonical content for this URL"
  • m
    i wonder if htmx should add a parameter to the request (but not the URL) to avoid this
  • p
    my guess is in middleware "hey this is an htmx response, do not cache"
  • m
    Copy code
    As discussed above, caching servers will by default match future requests only to requests with exactly the same headers and header values.
  • m
    > same headers and header values
  • m
    😑
1...265266267...1146Latest