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

Removing the Jackson leak in HttpHeaders #4597

Merged
merged 1 commit into from
Jul 26, 2019
Merged

Removing the Jackson leak in HttpHeaders #4597

merged 1 commit into from
Jul 26, 2019

Conversation

JonathanGiles
Copy link
Member

Instead registering a separate serializer directly with the JacksonAdapter. Tests that failed after functionality was removed from HttpHeaders now pass with the new HttpHeaderSerializer.

…ate serializer directly with the JacksonAdapter. Tests that failed after functionality was removed from HttpHeaders now pass with the new HttpHeaderSerializer.
@anuchandy
Copy link
Member

Some context: Why we need the ability to serialize HttpHeaders:

This is to support "header model type". Since http header type is a map when we serialize it we get a json string with key:values. The "header model type" will have properties with exactly the same key name (via jsonProperty attribute), now we can deserialize the json string to this strongly typed header model and return that to consumer.

@JonathanGiles JonathanGiles merged commit ea2f43a into Azure:master Jul 26, 2019
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.

2 participants