Login problem when deploy umbraco 13.10.0 as subsite

[GamoMan]

Which Umbraco version are you using?

13.10.0 (The other version get same problem)

Bug summary

I have login to the backoffice after success I get url /subsite/umbraco#/content after that it redirect to login page.
I have investigate and found that before it redirect I got 404 from this URL http://localhost/umbraco/backoffice/umbracoapi/authentication/IsAuthenticated

The subsite in URL is gone.

If I try to login again from the redirect URL login successfully but it redirect to root website.

Specifics

No response

Steps to reproduce

• Create subsite and deploy the Umbraco in subsite.
• Login it will redirect to login again.

Expected result / actual result

No response

[github-actions]

Hi there @GamoMan!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

I believe this is likely another effect of #19971 so I'll associate this issue too with the PR that resolves the problem, expected for 13.11.

[leekelleher]

Fixed in #19984 for v13.11.0.