Hide Forgot
Description of problem: lately, default dnssec-trigger http://ster.nlnetlabs.nl/hotspot.txt returning just "OK" doesn't work (returning 403 instead). So I tried to find a similar page and I found http://httpstat.us/ service, specifically for 200 code http://httpstat.us/200 . However this page returns "200 OK" text and I'm not able to configure dnssect-trigger to respect that. Based on the docs, this line in dnssec-triggerd.conf should do the trick: url: "http://httpstat.us/200 200 OK" but all I'm getting is "Wrong page content" error. I even tried to enclose the quoted string in single quotes or replace the space with %20 or using just 200 or OK but to no avail. Version-Release number of selected component (if applicable): dnssec-trigger-0.11-22.el7.x86_64 How reproducible: always Steps to Reproduce: 1. add url line from Description to your dnssec-triggerd.conf 2. restart the dnssec-triggerd service, wait for connectivity to settle, maybe choose "login" or "skip" in the applet 3. run dnssec-trigger-control status Actual results: http httpstat.us (23.99.0.12): error wrong page content Expected results: httpstat.us test page is matched successfully Additional info:
The actual problem is not caused by the whitespace in the HTTP probe result string, but by the fact that dnssec-trigger was not able to successfully accept anything longer than 2 characters. Fix submitted to upstream - https://open.nlnetlabs.nl/pipermail/dnssec-trigger/2017-March/000455.html
Fix has been merged by upstream https://github.com/NLnetLabs/dnssec-trigger/commit/947b7a8f41fa7b7a3bf06687910479cc41a1abda
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.