Open Rita003 opened 3 months ago
@adamint or @drewnoakes PTAL.
I cannot reproduce this, again. @Rita003 please re-test
@adamint I can repro this issue after installing the latest Aspire 8.1.1-preview.1.24380.4 in today's validation. You can try to run the project with https first, then run the project with http. The repro step as below:
dotnet run
dotnet run -lp http
@Rita003 could you try to repro once more? thanks.
This seems like an issue with how Safari manages cookies.
@adamint I can still repro this bug, it seems like an issue with Safari manages cookies. As described in the workaround: If we open Safari Settings > Click "Manage Website Data" in privacy page > Click "Remove All" to clear the localhost cookie history, then run the aspire project with http and open URL with token, it will not pop-up token page and works well
@adamint I can still repro this bug, it seems like an issue with Safari manages cookies. As described in the workaround: If we open Safari Settings > Click "Manage Website Data" in privacy page > Click "Remove All" to clear the localhost cookie history, then run the aspire project with http and open URL with token, it will not pop-up token page and works well
I don’t yet know where to file it, but this should be classified as an external bug on WebKit/Safari instead of Aspire. We should keep the issue here open until more investigation is done so that we can submit a comprehensive bug report, but I am fairly confident at this point in saying that this is not our bug
REGRESSION INFO: Also repro on Aspire 8.0.1
INSTALL STEPS
REPRO STEPS 1.Open CMD, create an Aspire App using following commands:
Set the "ASPIRE_ALLOW_UNSECURED_TRANSPORT": "true" in the launchSettings.json of the aspire.AppHost project
Dotnet run the project in CMD, and open URL with token:
dotnet run
Go back to the Command Prompt and enter "Ctrl + C" to shut down the application
Run the project with http in CMD, and open URL with token:
dotnet run -lp http
ACTUAL: There is no response and can't go to aspire dashboard page, if copy the URL token to browser, it still cannot log in.
Workaround
NOTE:
dotnet run
the project.EXPECTED Open URL with token not pop-up token page and works well