Relative frame src not resolved properly when prefetched on hover that results in 302

[kuba-orlik]

There's a link in a navbar with href pointing to /a

The /a endpoint redirects with 302 to /a/b/

The HTML returned by /a/b/ includes a turbo-frame with src set to a relative url: ./frame.

When opening a new tab and visiting the /a/b endpoint directly, the frame loads properly - the browser requests the /a/b/frame URL.

However, when the user starts on the homepage (/), and then clicks on a link that points to /a, the /a/b/ page appears, but the frame tries to load from /frame instead of /a/b/frame.

It seems that when turbo is prefetching the HTML and parsing the incoming HTML, the relative URLs are parsed relative to the URL that the user is currently on - not the URL that the redirect leads to.