First breakpoint on line 670 and second breakpoint on line 671, running through nulls System.Web.HttpContext.Current.
However breaking on line 670 and stepping over F10 keeps context, and gives normal results.
Test case with GET did not hit this line.
Requests are executed on the browsers worker thread, no additional threads are spawned, the fix will be finding out when to use .ConfigAwait() and when not to but without a repro I wont be able to verify it.
Is there a reason you’re linking to the older version of RestHandler as the latest version calls .ConfigAwait(); on CreateRequestAsync:
If you can provide a repro I can identify and resolve it, otherwise if you’re running a local version of ServiceStack can you try adding or removing .ConfigAwait() to check if it resolves it and let me know and I’ll update accordingly.