MapStaticAssets breaks endpoint routing in container

[bradmarder]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Including MapStaticAssets() in my dev environment within a Docker container will cause POST requests to return 405 HTTP Method Not Supported. Removing that one line of code fixes the issue. I have zero assets for dev, but a few for prod, and a different docker setup, but it all works perfectly there.

Expected Behavior

MapStaticAssets() should not break endpoint routing (unless there is some naming conflict of files/paths)

Steps To Reproduce

Sorry I have no time for a simple repro, so this is all I have. https://github.com/bradmarder/LootGod

I normally just run docker compose watch to start it all up, and it seems any POST request will fail.

Exceptions (if any)

405 HTTP Method Not Supported

.NET Version

9.0.102

Anything else?

It took me quite a bit of time to figure out MapStaticAssets() was causing the issue, especially since the error and symptoms and diagnosing process were all so weird. Also I'm using a WebApplicationFactory and HttpClient to run tests on every endpoint, and they all pass.

[MackinnonBuck]

Sorry I have no time for a simple repro, so this is all I have

Thanks for providing the repro, @bradmarder. Unfortunately, we would need a more stripped down, minimal repro in order to continue this investigation. I appreciate that you mentioned you don't have time to provide a simple repro, but I'm going to mark this issue as "Needs: Repro" just in case you or someone else happens to be able to reproduce this in a simpler app. If not, this issue will auto-close in a week. Feel free to open a new issue if you're able to reproduce this again in a simpler app after this issue gets closed.

Thanks again 🙂

[dotnet-policy-service]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.