aboutsummaryrefslogtreecommitdiffstats
path: root/EPLICENCE
diff options
context:
space:
mode:
authorAnders Svensson <[email protected]>2013-05-31 14:46:59 +0200
committerAnders Svensson <[email protected]>2013-06-02 15:00:19 +0200
commit21e778b998b895034453251d83c3e6aaa72fe395 (patch)
tree1157816c06423b0eed15310537e77c58aafe161b /EPLICENCE
parent22685099ace9802016bf6203c525702084717d72 (diff)
downloadotp-21e778b998b895034453251d83c3e6aaa72fe395.tar.gz
otp-21e778b998b895034453251d83c3e6aaa72fe395.tar.bz2
otp-21e778b998b895034453251d83c3e6aaa72fe395.zip
Fix setting of Failed-AVP on {answer_message, 5xxx} from handle_request
RFC 6733 says that certain 5xxx result codes must be accompanied by Failed-AVP, and decode populates #diameter_packet.errors with Result-Code/AVP pairs for errors it detects. However, Failed-AVP was not set in the outgoing answer if the handle_request callback returned {answer_message, 5xxx}. It is now set with the AVP from the first pair with the specified Result-Code, if found. Note that {answer_message, 5xxx} doesn't handle all cases in which a 5xxx answer is required, only that in which the setting above is appropriate. If it isn't then handle_request should construct its answer and return {reply, Ans}.
Diffstat (limited to 'EPLICENCE')
0 files changed, 0 insertions, 0 deletions