Skip to content

Add remark on YARP forwarder destination prefix #35638

Closed
@guardrex

Description

@guardrex

Description

Per dotnet/blazor-samples#555 (comment) ...

I discovered a little more about how the forwarder destination prefix works. For the example in it's current form, the correct backend to call is found using either https://weatherapi or https://localhost:7277 for the destination prefix ...

app.MapForwarder("/weather-forecast", "{DESTINATION PREFIX}", transformBuilder =>

Presumably, it can find it via its launch settings address where the web API is running, but the ability to use https://weatherapi comes from ...

ar weatherApi = builder.AddProject<Projects.MinimalApiJwt>("weatherapi");

... in the Aspire.AppHost config.

It makes sense to leave the https://weatherapi prefix in place, but I'd like to call out the connection in the article.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/security/blazor-web-app-with-entra?view=aspnetcore-9.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/security/blazor-web-app-with-entra.md

Document ID

58758d13-94c9-e208-e0f6-16676834413c

Platform Id

1c89a093-14c3-881b-7297-49c7c6cb4ea1

Article author

@guardrex

Metadata

  • ID: 58758d13-94c9-e208-e0f6-16676834413c
  • PlatformId: 1c89a093-14c3-881b-7297-49c7c6cb4ea1
  • Service: aspnet-core
  • Sub-service: blazor

Related Issues

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions