You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...but there is nothing like that in .UseOxpecker(endpoints) and the Microsoft.AspNetCore.Hosting.ListenOptionsHttpsExtensions.UseHttps takes some ListenOptions which I don't know where to get.
Do I even need that, if I just bind a certificate to a port
e.g. via classic netsh http add sslcert ipport=0.0.0.0:443 certhash=(thumbprint) appid=(someGuid) ?
The text was updated successfully, but these errors were encountered:
@Thorium Kestrel configuration is orthogonal to Oxpecker, Oxpecker is just a middleware. Any "Minimal APIs" https configuration that you find will be applicable to Oxpecker as well.
Thank you for the quick reply. It seems the underlying Kestrel configurations have changed around AspNetCore 6, and the internet still has a lot of old docs. I have to investigate the best practices tomorrow.
I'm trying to find example documentation on configuring Oxpecker to use HTTPS, but the documentation is a bit thin on that part.
The AspNetCore 6 documentation says:
...but there is nothing like that in
.UseOxpecker(endpoints)
and theMicrosoft.AspNetCore.Hosting.ListenOptionsHttpsExtensions.UseHttps
takes someListenOptions
which I don't know where to get.Do I even need that, if I just bind a certificate to a port
e.g. via classic
netsh http add sslcert ipport=0.0.0.0:443 certhash=(thumbprint) appid=(someGuid)
?The text was updated successfully, but these errors were encountered: