Response from HX-Location should respect HX-Push-Url header

I have a scenario where I set the `HX-Location` header to redirect the client to other page (assume `/x`). In some cases, the response (of `/x`) could contain `HX-Push-Url` header (assume `/y`) which is not being respected, i.e., the page url is still same as the url in `HX-Location` header (`/x`).

Is there a way to push the url in `HX-Push-Url` (`/y`) header of response in browser history after the redirect using `HX-Location` header?