Hello 👋,
This issue does not seem to be related to ABP. However, I have searched a bit and unfortunately there is no other solution as far as I can see. See more: https://stackoverflow.com/a/3726846/9922629
Hi,
Thank you for the information you have provided. In addition, can you share the log records of the backend host application?
Hello 👋
If possible, please send your solution to support@abp.io, including the ticket number (#9445) in the subject or body of the email. So that I can help you faster.
Best regards, Berkan Şaşmaz Developer Advocate https://www.berkansasmaz.com
Hello,
What kind of exception do you get when sending a request from the web side? Also, do you have a chance to share your gateway configurations?
If possible, please send your solution to support@abp.io, including the ticket number (#9445) in the subject or body of the email.
Best regards,
Berkan Şaşmaz
Developer Advocate
https://www.berkansasmaz.com
Hello, I tried to reproduce the problem with the application you provided, but when I added the relevant scope and client, I was able to log in successfully. You can find the screenshot below:
Below you can find the information of the scope and client I added:
Hello, I downloaded your solution and noticed that your NuGet API key and other sensitive information are publicly exposed. I kindly recommend that you delete the solution from your drive immediately to protect your data.
Hi,
First of all, thank you very much for the information you have provided.
.NET Aspire provides opinionated templates. In the article, the ServiceDefaults project is created using dotnet commands without any additional customization. Since these templates are opinionated, some configurations—such as retry timeout durations—are pre-configured based on common scenarios.
However, these default settings may not suit your specific needs or certain endpoints. In such cases, you should customize the configuration accordingly. For instance, if you have non-idempotent methods, you might want to disable the retry mechanism altogether.
You can also disable retries specifically for POST methods using the following configuration:
httpClientBuilder.AddStandardResilienceHandler(options =>
{
options.Retry.DisableFor(HttpMethod.Post);
});
For more information: https://learn.microsoft.com/en-us/dotnet/core/resilience/http-resilience?tabs=dotnet-cli#disable-retries-for-a-given-list-of-http-methods
I highly recommend reading this article on how you can fine-tune it: https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter
Hi,
If it is possible, can you send your solution to support@abp.io email address (with the ticket number - #9325). Regards.
Hi,
You can share your solution if it's possible or full log records via email (to support@abp.io with ticket number).
Regards.
Hello,
If the database was created before and the data was seeded, the data may not be updated when it runs again. Because when we seed data, we almost always look at the number of records and if there is a record, we do not seed again. Thus, we do not seed duplicated data.
Does the problem persist when you delete and regenerate the database with DbMigrator?
In addition, does this problem only occur on a single endpoint? And does it also occur local development environment?
