-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Pevent merging of repeated values in headerMap when using custom handlers #2099
Conversation
@@ -237,4 +237,4 @@ namespace CefSharp | |||
} | |||
}; | |||
} | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revert this please
@@ -1,4 +1,4 @@ | |||
// Copyright � 2010-2017 The CefSharp Authors. All rights reserved. | |||
// Copyright © 2010-2017 The CefSharp Authors. All rights reserved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revert this please
String^ value = headers[key]; | ||
result.insert(std::pair<CefString, CefString>(StringUtils::ToNative(key), StringUtils::ToNative(value))); | ||
for each(String^ value in headers->GetValues(key)) | ||
result.insert(std::pair<CefString, CefString>(StringUtils::ToNative(key), StringUtils::ToNative(value))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Braces around the body of the loop please
Made some comments inline |
…s under the same key, with ",". This breaks some headers, like the "Set-Cookie"; where the "." has another meanings according to RFC.
requested changes done. |
thanks @merceyz for your feedback. i've made the changes you reviewed. |
Thank you |
The NameValueCollection auto merges (according to MSDN) all the values under the same key, with ",".
This breaks some headers, like the "Set-Cookie"; where the "." has another meanings according to RFC.
as far as i've seen, this issue will be present everytime a customhandler is used.