-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Fix quality factor handling (NRE in MediaTypeWithQualityHeaderValueComparer) #1141
Comments
@PinpointTownes , Can you please share the app I am unable to repro your scenario with GET http://localhost:42750/Binding/Action HTTP/1.1 |
Still doesnt repro: Could you tell me what is the version you are running against ? |
The same one:
|
Okay, issue found: Using I'd also add a null check in |
@PinpointTownes thanks for your help investigating this. There's another |
@PinpointTownes thanks for your help in getting to the bottom of this, @rynowak yes we should fix that as well. |
@rynowak @harshgMSFT thanks 🎉 |
… QualityFactor we throw. Fix: Imitating the same behavior as it is in WebApi. We ignore the entire header even if one part of it is invalid.
… QualityFactor we throw. Fix: Imitating the same behavior as it is in WebApi. We ignore the entire header even if one part of it is invalid.
… QualityFactor we throw. Fix: Imitating the same behavior as it is in WebApi. We ignore the entire header even if one part of it is invalid.
… QualityFactor we throw. Fix: Imitating the same behavior as it is in WebApi. We ignore the entire header even if one part of it is invalid.
Checked in. Please see - 0d8a736 |
@sornaks it works like a charm, thanks sir! 👍 |
When returning negotiable content, an exception is thrown in
MediaTypeWithQualityHeaderValueComparer.CompareBasedOnQualityFactor
if theAccept
header contains a quality factor:The text was updated successfully, but these errors were encountered: