mirror of
https://github.com/BepInEx/mono.git
synced 2026-11-19 01:31:17 -10:00
There was apparently no point in the call flow when the reponse message was set in the context, resulting in WebOperationContext.IncomingResponse always being null. After patching WebMessageFormatter to set the response in the context (if available) the value of WebOperationContext.IncomingResponse was still null. A bit more investigation showed that IncomingWebResponseContext would construct a HttpResponseMessageProperty encapsulating the OperationContext at the time the request was made but before the response was received and cache that object. That caused the HttpResponseMessageProperty to always have a null value for the response. The second part of the patch changes this behavior and always creates a new HttpResponseMessageProperty on GET.