diff options
| author | Anders Svensson <[email protected]> | 2015-06-29 09:09:13 +0200 |
|---|---|---|
| committer | Anders Svensson <[email protected]> | 2015-08-04 17:33:37 +0200 |
| commit | abd6c7494f973eb91c6a582f3370e9896d28992b (patch) | |
| tree | 8e51dccebf3c0a200867cbb40f51b68882bf40f7 /otp_patch_apply | |
| parent | 80420620b67216b67e90affc5fe35505207254a3 (diff) | |
| download | otp-abd6c7494f973eb91c6a582f3370e9896d28992b.tar.gz otp-abd6c7494f973eb91c6a582f3370e9896d28992b.tar.bz2 otp-abd6c7494f973eb91c6a582f3370e9896d28992b.zip | |
Don't flag AVP as missing as a consequence of decode error
The decode of an incoming Diameter message uses the record
representation to determine whether or not an AVP has been received with
the expected arity, the number of AVPs in each field following decode
being compared with the arity specified in the message grammar. The
problem with this is that decode failure isn't reflected in the record
representation, so that an AVP can be appended to the errors field of a
diameter_packet record despite an entry for the same AVP already
existing. This isn't a fault as much as a misleading error indication,
but now only append AVPs that aren't already represented.
Diffstat (limited to 'otp_patch_apply')
0 files changed, 0 insertions, 0 deletions