In 8.3.2, there are 2 issues compared to 8.2.3
v8.2.3
v8.3.2
v8.2.3
v8.3.2
@maliming I use ABP's built-in login completely. AuthServer is a separate project. Where can I change to achieve my desired result?
hi
This is ASP NET Core behavior.
https://learn.microsoft.com/en-us/aspnet/core/security/anti-request-forgery?view=aspnetcore-8.0#multiple-browser-tabs-and-the-synchronizer-token-pattern
@maliming Is there any way to bypass this behavior on ABP?
Hello ,
I have tried to reproduce your issue , it works fine at my end. you may check this Sample Application
Please provide me details steps to reproduce issue or screenshots , logs of error so that I can better assist you.
Thank you.
The reproduction sequence I described at the beginning, below is the error screen image
sorry zero-downtime deployments
I understand. First of all, does ABP Commercial have a system to support non-startup releases?
Ok, where should I contact for help?
Thank you for the suggestion. I understand that using migrationBuilder.Sql allows us to add custom SQL during migration. However, I'm looking for a way to achieve this directly through EF Core's built-in migration functionality without having to manually insert SQL statements.
Our goal is to keep our migration process as consistent and maintainable as possible within the framework provided by EF Core. If there is an alternative approach or any upcoming features that might support this requirement natively, I would appreciate any guidance or suggestions you could offer.
Thank you for reaching out.
It is possible to use ALGORITHM=INSTANT without ABP Commercial. However, when using EF Core for migrations, applying specific options like ALGORITHM=INSTANT to an ALTER TABLE command might require manually running the SQL or customizing the migration scripts to include this option.
If EF Core migrations do not support this option by default, we might need to consider executing custom scripts before or after the migration to ensure the database lock is minimized.
Our goal is to achieve zero-downtime releases by minimizing database locks. We would appreciate any further guidance or suggestions you could provide on this matter.
Best regards,
