@resmo Actually, the docs say it's like clicking a `<a href=... hx-boost="true">` and also "This response header can be used to trigger a client side redirection without reloading the whole page."

So in that case I think it's pretty clear. If you really want a full redirect you can use HX-Redirect.

But I get your point, it may indeed be clearer to separate HTMX and non-HTMX endpoints.

Btw, I don't consider HTMX to be a particularly new project. It's already been at version 2.x for almost two years, 1.0.0 was released in 2020, and its predecessor - intercooler.js - had its 1.0.0 release in 2016. So roughly 10 years in one form or another. That's a lot these days where there's a new hyped client-side JS framework every other week.

@cuboci Well, yeah for a js framework it's proably long enough.

there are 2 headers, hx-redirect and hx-location, hx-redirect does a redirect but the issue is (but probably I did it wrong), it also ads a header of hx-request=true so if you have 2 identical URI for hx requests and non-hx requests, it would take the hx entry point and is not what the docs says IMHO.

@cuboci no, let me clarify my thoughts:

I set a response header hx-redirect, htmx will trigger a client side redirect. right.

however as written here https://htmx.org/reference/#headers the request header hx-request is always true

that means (IMHO) it is just like a hx-get requests, not a "normal" http get request (only diff is hx-request request header=true)

as a result, your handler for hx requests is the entry point, not a non hx-request entrypoint, which may be unexpected and this is what I see.