Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1374383 - HTTP probe result length could not be longer than 2 characters
Summary: HTTP probe result length could not be longer than 2 characters
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dnssec-trigger
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Osvald
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1380362 1388055
TreeView+ depends on / blocked
 
Reported: 2016-09-08 14:20 UTC by David Jaša
Modified: 2019-06-20 15:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1388055 (view as bug list)
Environment:
Last Closed: 2019-06-20 15:22:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Jaša 2016-09-08 14:20:16 UTC 
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:
Comment 1 Tomáš Hozza 2017-03-06 11:16:48 UTC 
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
Comment 2 Tomáš Hozza 2017-07-04 13:09:22 UTC 
Fix has been merged by upstream https://github.com/NLnetLabs/dnssec-trigger/commit/947b7a8f41fa7b7a3bf06687910479cc41a1abda
Comment 5 RHEL Program Management 2019-06-20 15:22:18 UTC 
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.