Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mtom fixes #5069

Merged
merged 2 commits into from
Mar 31, 2023
Merged

Mtom fixes #5069

merged 2 commits into from
Mar 31, 2023

Conversation

mconnew
Copy link
Member

@mconnew mconnew commented Mar 29, 2023

Fixes #4831
Also exposes UserNameSecurityToken as without it you can't use the token returned from the SecurityTokenProvider when using UserName credentials.

@HongGit
Copy link
Contributor

HongGit commented Mar 30, 2023

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mconnew
Copy link
Member Author

mconnew commented Mar 30, 2023

This is failing because writeMessageHeaders should only be false for Http (as it has its own HTTP headers). WebSockets don't have per-request headers which is why these headers are added to the body. I need to work out how to differentiate between them and try to do it without exposing new API. One option is to add a message property which specifies whether to write message headers, with it defaulting to true and Http specifying false.

@mconnew mconnew merged commit ba71500 into dotnet:main Mar 31, 2023
@mconnew mconnew deleted the MtomFixes branch October 11, 2023 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mtom Encoding .Net6 vs .Net Framework
2 participants