Signed-off-by: Remi Gacogne <remi.gacogne@powerdns.com>
- name: "ERCode"
description: "Reply immediately by turning the query into a response with the specified EDNS extended rcode"
skip-cpp: true
- changes:
- - version: 2.1.0
- content: "The ``rcode`` parameter used to be an unsigned integer and is now a string"
parameters:
- name: "rcode"
type: "RCode"
description: "Whether subsequent rules should be executed after this one"
- name: "RCode"
description: "Reply immediately by turning the query into a response with the specified rcode"
- changes:
- - version: 2.1.0
- content: "The ``rcode`` parameter used to be an unsigned integer and is now a string"
skip-cpp: true
parameters:
- name: "rcode"
description: "The EDNS version to match on"
- name: "ERCode"
description: "Matches queries or responses with the specified rcode. The full 16bit RCode will be matched. If no EDNS OPT RR is present, the upper 12 bits are treated as 0"
- changes:
- - version: 2.1.0
- content: "The ``rcode`` parameter used to be an unsigned integer and is now a string"
parameters:
- name: "rcode"
type: "RCode"
description: "The qtype, as a numerical value"
- name: "RCode"
description: "Matches queries or responses with the specified rcode"
- changes:
- - version: 2.1.0
- content: "The ``rcode`` parameter used to be an unsigned integer and is now a string"
parameters:
- name: "rcode"
type: "RCode"
Upgrade Guide
=============
-2.0.x to 2.1.0
---------------
-
-Since 2.1.0, ``rcode``s in the ``YAML`` configuration can be specified either by their case-insensitive names (e.g. ``refused``), or by their numerical values (e.g. ``"5"``). Unfortunately in some contexts (:func:`RCodeRule`, :func:`ERCodeRule`, :func:`RCodeAction` and :func:`ERCodeAction`) this has the side-effect that a numerical value (``5``) is no longer accepted and has to be converted to a string (``"5"``).
-
1.9.x to 2.0.0
--------------