Add endpoint restrictions to the documentation

[camiteca]

Hi there,

I was trying to publish beatpulse on IIS. Since I already gave it an application Url (/beatpulse-ui), I didn't need the host to also publish the app under /beatpulse-ui. I tried using string.empty but couldn't publish the app, so I looked into the code and I saw that a "/" was needed instead.

BeatPulse/src/BeatPulse.UI/BeatPulseApplicationBuilderExtensions.cs

Line 41 in 7fe5019

if (string.IsNullOrEmpty(path) || !path.StartsWith("/"))

How would you aproach this? Maybe be permissive and allow string.empty as well as "/"? Or just add a comment on the docs?

Thanks.

[CarlosLanderas]

To bind middleware into the pipeline the request path has to start with slash. What we can do is allow using string.Empty and internally bind it to "/". Is that what you mean?.

Thanks!

[camiteca]

Either that or just adding what you've just commented as part of the docs. :)

[CarlosLanderas]

I'm gonna bind the string.empty to "/", as it make sense. Thanks @karlmtc ;)

[camiteca]

I'm looking into this and it seems that slash is also not allowed. I'm getting this error:

It may be related to this issue: aspnet/HttpAbstractions#683

[camiteca]

It seems that in order to map a route to '/', you need to just call Run (not Map).

https://docs.microsoft.com/es-es/aspnet/core/fundamentals/middleware/?view=aspnetcore-2.1#use-run-and-map

Does it make sense for you to allow a change on how the Urls are mapped?