Null value in the static HttpContext.Current property when used from a thread worker #949
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The static HttpContext.Current property returns null when the calling-thread is not the same thread that was associated with the current HTTP request/response, because HttpContext.Current uses thread-local storage.
To address this, a workaround is added specifically for calls from objects with UseBigStack enabled. Which resolves the wrong value returned by the GxHttpContext.IsHttpContext method.
Issue:106662