Hello Mark,
On 11 Sep 2015, at 0:30, Mark Strother wrote:
In 3.4.2 the HTTP backend removed the priority field. The priority
value
was the first value in the content string. In 3.4.5 the behaviour has
reversed and including the priority in the content string causes an
error.
I can't find it documented anywhere. Is this intentional behaviour or
there
a regression issue?
The intention is that priority remains part of content, as you appear to
see correctly on 3.4.2. If 3.4.5 appears to reverse this behaviour, this
would be a regression.
Can you show your failing requests and the responses you get?
Kind regards,
--
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/
_______________________________________________
Pdns-dev mailing list
Pdns-dev@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-dev
