Skip to content

Conversation

@yaananth
Copy link

@yaananth yaananth commented Dec 22, 2017

see https://github.com/aspnet/Docs/pull/5054/files

I don't know where we place warnings generally, but I placed it under "Remarks"

@yaananth yaananth changed the title Add warning about usage of PreSendRequestHeaders Add warning about usage of PreSendRequestHeaders and PreSendRequestContent Dec 22, 2017
@Rick-Anderson
Copy link
Contributor

Looks good.

Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution @yaananth. I've left some feedback for you to consider. The same comment would apply to the 2nd change.

For more information about how to handle events, see [NIB: Consuming Events](http://msdn.microsoft.com/en-us/01e4f1bc-e55e-413f-98c7-6588493e5f67).
> [!WARNING]
> Do not use `PreSendRequestContent` with managed modules that implement `IHttpModule`. Setting these properties can cause issues with asynchronous requests. We have seen instances where the combination of Application Requested Routing(ARR) and websockets lead to access violation exceptions (iiscore!W3_CONTEXT_BASE::GetIsLastNotification+68 in iiscore.dll has caused an access violation exception (0xC0000005)) that lead to w3wp crashing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing space between term and acronym: Application Requested Routing (ARR)

The use of we is not recommended unless we're using it to refer to we Microsoft recommends. Also the last sentence is a bit hard to parse giving it has lead 2x and that info on parentheses breaking the flow. I'm wondering if that info is really needed.

Maybe something like this?
"The combination of Application Requested Routing (ARR) and websockets might lead to access violation exceptions that can cause w3wp to crash. For example, iiscore!W3_CONTEXT_BASE::GetIsLastNotification+68 in iiscore.dll has caused an access violation exception (0xC0000005)."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mairaw I think that's the MS recommendation.

I like your rewrite.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's in the style guide @Rick-Anderson. I'm glad you liked it. Thanks!

yaananth added a commit to yaananth/Docs that referenced this pull request Dec 22, 2017
@yaananth
Copy link
Author

@mairaw Addressed.
Also dotnet/AspNetCore.Docs#5067 for the other repo

Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making the suggested changes @yaananth. I'll merge as soon as I can verify the build and changes should be live in the next day or so.

@mairaw mairaw added verify-build-before-merge ✨ 1st-time docs contributor! Indicates PRs from new contributors to the docs repository and removed verify-build-before-merge labels Dec 22, 2017
@mairaw mairaw merged commit f7b2a4d into dotnet:master Dec 23, 2017
Rick-Anderson pushed a commit to dotnet/AspNetCore.Docs that referenced this pull request Dec 27, 2017
cillroy pushed a commit to dotnet/AspNetDocs that referenced this pull request Jan 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✨ 1st-time docs contributor! Indicates PRs from new contributors to the docs repository

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants