dotnet / dotnet/systemweb-adapters
SessionServer returns 404 from .net framework, help needed
- Dominant language
- C#
- Stars
- 384
- Forks
- 76
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 1
Description
I'm hoping I've missed something simple here. Our .net framework app is using Unity DI which may be related to the issue. I see exceptions from Unity being unable to resolve constructors for things like `System.Web.Http.Dispatcher.IAssembliesResolver` but I believe these are red herrings as the services used internally in systemweb-adapters should fallback to default services when null is returned?
The setup for sessionserver in Global.asax.cs Application_Start is as follows. I've tried with and without proxy support options and many different endpoints. We have a redirect set up for any unknown request not starting in `/api` so I haven't tested the default of `/systemweb-adapters/session`
I'm unable to access the /api/test, either from .net core or directly myself to see if the endpoint is live. Our .net core app is running in a docker container on 443 and the .net framework app is on IIS on windows on 32773. The .net framework app is hosted on a virtual directory subfolder so the site structure is a website called 'app' with a virtual directory called 'app' which is where the site lives.
I've tried setting the basepath in the container to '/app' as well as I saw something about mirroring virtual directories but with no success. I don't see any sort of relevant error in the logs for .net framework.
Any help on this would be greatly appreciated
```
SystemWebAdapterConfiguration.AddSystemWebAdapters(this)
.AddSessionSerializer()
.AddProxySupport(options =>
{
options.ServerPort = 32773;
options.UseForwardedHeaders = true;
options.Scheme = "https";
}
)
.AddJsonSessionSerializer(options =>
{
// Register every session key here
options.RegisterKey("TestKey");
})
.AddRemoteAppServer(options => { options.ApiKey = "54b69938-90dd-4f79-adcd-27fbd6f0e4b7"; })
.AddSessionServer(options =>
{
options.SessionEndpointPath = "/api/test";
});
```
Contributor guide
Assessment
This issue has not been assessed yet.