Last post Mar 30, 2019 06:56 PM by bruce (sqlwork.com)
Mar 30, 2019 06:14 AM|Fabolt|LINK
for a project I want to use a asp.net core webapi project. However I came across a limit of using a custom HTTP version/protocol name using kestrel.
The line of that protocol starts with POST /Sts/Connect STS/1.0 and I found no way to change how that processing in asp.net core works. Currently I'm always facing a "Unrecognized
HTTP version" exception.
I'm open for any ideas. Otherwise I have to fallback to a simple socket server and handle all these things on my own.
Mar 30, 2019 06:56 PM|bruce (sqlwork.com)|LINK
did you write a custom connection handler? see;