Re: [Pdns-users] Need help with PowerDNS Remote HTTP Backend

2016-01-10 Thread Aleksey Chudov
Python BaseHTTPServer by default uses HTTP/1.0 and it does not add content-length header automatically after switching to HTTP/1.1. Thanks for clarifying that. On Sat, Jan 9, 2016 at 5:23 PM, Aki Tuomi wrote: > It works if you use HTTP/1.1 compatible responses. RFC says that you either > need t

Re: [Pdns-users] Need help with PowerDNS Remote HTTP Backend

2016-01-09 Thread Aki Tuomi
It works if you use HTTP/1.1 compatible responses. RFC says that you either need to send your response chunked or set content-length. YaHTTP will check and enforce this. Aki On Sat, Jan 09, 2016 at 11:10:19AM +0200, Aleksey Chudov wrote: > Finally I found the cause of the problem. PowerDNS Remote

Re: [Pdns-users] Need help with PowerDNS Remote HTTP Backend

2016-01-09 Thread Aleksey Chudov
Finally I found the cause of the problem. PowerDNS Remote HTTP Backend works only with 'Content-Length' header. So, the following code works until 'Content-Length' header exists. import BaseHTTPServer class HTTPRequestHandler(BaseHTTPServer.BaseHTTPRequestHandler): def do_GET(self):

Re: [Pdns-users] Need help with PowerDNS Remote HTTP Backend

2016-01-08 Thread Aleksey Chudov
Some more information. I have tested pdns-static_3.4.7-1_amd64.deb on Debian and pdns-3.4.7-1.el7.x86_64 + pdns-backend-remote-3.4.7-1.el7.x86_64 on CentOS 7.2 with no success. Also I have tried manually reply to pdns request using netcat utility. As can be seen pdns sends next request just after

[Pdns-users] Need help with PowerDNS Remote HTTP Backend

2016-01-08 Thread Aleksey Chudov
Hi, I'm trying to implement simple PowerDNS Remote HTTP Backend in Python. Below is test code just like https://doc.powerdns.com/md/authoritative/backend-remote/#scenario-soa-lookup-with-http-connector import BaseHTTPServer REPLY = """{ "result": [ { "qtype": "SOA", "qname": "e