Gurinder Singh
Gurinder Singh
Linking with `link.exe` on Windows works fine as well. It is in fact easier than linux because you don't need cross compilation. All you do is pass the flag `/subsystem:EFI_APPLICATION`...
@wiltaylor Any update on this?
A quick debugging session showed that we're setting the content length correctly for `HEAD` requests: https://github.com/TheWaWaR/simple-http-server/blob/108275b77217c8c5bfe90671d7d50ea1b2c9e2d7/src/main.rs#L683 which is identical to how we set it for `GET` requests: https://github.com/TheWaWaR/simple-http-server/blob/108275b77217c8c5bfe90671d7d50ea1b2c9e2d7/src/main.rs#L781 Yet it...
Thanks @TheWaWaR. I agree with you. I should've ideally done the fix, but I'm in the middle of a lot of stuff right now. So will have to do this...
It's an Iron bug. I've filed an issue there: https://github.com/iron/iron/issues/582
Will have to move to the new version of `Iron` to get this fix released.
`RequiredScope` used to work as expected in this issue until version 1.17.0 of Microsoft.Identityt.Web. It got broken in 1.18.0. See these issues: https://github.com/AzureAD/microsoft-identity-web/issues/1609 https://github.com/AzureAD/microsoft-identity-web/issues/1002. In my case adding `builder.Services.AddRequiredScopeAuthorization()` statement...
@jmprieur Yes, I peeked inside Microsoft's code and saw `'AddRequiredScopeAuthorization()` being used there and simply mimicked that. It may well have been `AddMicrosoftIdentityWebApi()` that I peeked into (don't exactly remember...
Thanks @agalakhov One way to do zero-copy might be for `tungestnite` to not attempt assembly of partial messages into a single `Message` object while receiving or require a full `Message`...
You're right about ping and close. We may not be able to avoid assembly for them, but they are generally very small, so they'd rarely fragment and therefore it should...