NavigationManager.NavigateTo ignores base URI

[MV10]

I'm altering a large Blazor server-side app which was originally developed under IIS Express (with localhost etc) to support deployment to an IIS virtual directory. Parts of the app have data-driven navigation where pages are referenced just as they're declared in the @page directives (e.g. /mycontent). We've specified the virtual directory in startup with UsePathBase so we were surprised when calls like this ignore the base:

NavManager.NavigateTo("/mycontent", forceLoad: true);

Instead of https://site.com/virtualdir/mycontent it navigates to https://site.com/mycontent which 404s.

It's easily fixed, but is this intentional, or is this a bug?

(Edit: Probably worth noting that ToAbsoluteUri also ignores the base.)

[javiercn]

@MV10 thanks for contacting us.

You need to setup the base url with the document base href tag on your _Host.cshtml that's the only thing Blazor will use to determine the base url.

Also,

NavManager.NavigateTo("/mycontent", forceLoad: true);

is a host relative url, you need to remove the forward slash to make it a base relative url.

[MV10]

@javiercn thanks, I have specified base href, but I used ~/ ... is that a problem? I confirmed it expands appropriately when it reaches the browser.

remove the forward slash to make it a base relative url

I just realized this means you can't use '/' to navigate back to the default content (of course, BaseUri will get you there, but still, it seems counterintuitive).

[mkArtakMSFT]

To navigate to the base uri you can use empty string. In your example however, simply remove the leading / and it will work.

NavManager.NavigateTo("mycontent", forceLoad: true);

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.