The OrchardCore.Cors module seems to be broken.

[hyzx86]

The OrchardCore.Cors module seems to be broken.
After adding the following code in Program.cs, the cross-domain access works fine

builder.Services.AddCors(options =>
{
    options.AddDefaultPolicy(builder =>
    {
        builder.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader();
    });
});
....
app.UseCors();

[hyzx86]

relate ：#15416 (comment)

[hyzx86]

I remember this was a problem a year ago, but it was fixed, and now it's back

[hishamco]

Could you please submit a PR?

I remembered there was a PR related to CORS, I'm not sure if it's the main reason for this issue

[hyzx86]

Could you please submit a PR?

I remembered there was a PR related to CORS, I'm not sure if it's the main reason for this issue

Sorry, it was hardcoded in my 'Program.cs' file and I haven't found the real reason yet.
Probably because of the order in which modules are loaded.

[hishamco]

I'm not sure if it's related to #15486, @hyzx86 could you please write the steps to reproduce, I might investigate on this

[hyzx86]

I'm not sure if it's related to #15486, @hyzx86 could you please write the steps to reproduce, I might investigate on this

I'm trying to locate the problem,
Initially I got the package from Nuget and found that the cross-origin feature wasn't working,
Then I packaged from the source code locally and replaced the dll file in my native solution, the problem still existed.
I noticed that your code seems to be tweaking the packing process, so this issue is probably not related to the bundling process

[hyzx86]

Using the following recipe test, it turns out that this problem does not exist in the OC source code, the problem may be in my custom code, I need to check where is incompatible with the existing code.

Here is my recipe
Recipe.json

[hishamco]

Happy to hear that