You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the end of processing a post request, I'd like the browser to send a boosted GET request to URL x, so I respond to the post request with an hx-location response header set to URL x (along with a 204 response).
The browser does send the GET request to URL x, but it's not boosted (no hx-boost request header).
This response header can be used to trigger a client side redirection without reloading the whole page. Instead of changing the page’s location it will act like following a hx-boost link, creating a new history entry, issuing an ajax request to the value of the header and pushing the path into history.
What am I missing here? Shouldn't the GET request triggered by the hx-location response header have an hx-boost: true request header?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
At the end of processing a post request, I'd like the browser to send a boosted GET request to URL
x, so I respond to the post request with anhx-locationresponse header set to URLx(along with a 204 response).The browser does send the GET request to URL
x, but it's not boosted (nohx-boostrequest header).The HX-Location header documentation states that:
What am I missing here? Shouldn't the GET request triggered by the
hx-locationresponse header have anhx-boost: truerequest header?Beta Was this translation helpful? Give feedback.
All reactions