This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4266 - Validator 0.7.4 intalled locally will not operate on a private subnet
Summary: Validator 0.7.4 intalled locally will not operate on a private subnet
Status: RESOLVED WORKSFORME
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: HEAD
Hardware: PC Windows 2000
: P2 blocker
Target Milestone: ---
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-19 22:27 UTC by Lynn Wheelwright
Modified: 2007-01-20 00:34 UTC (History)
0 users

See Also:

Attachments

Description Lynn Wheelwright 2007-01-19 22:27:24 UTC 
Version 0.7.2 when installed locally will operate on a private local subnet.  When I upgraded to 0.7.4 (hoping to pick up some bug fixes).  This mode of operation no longer works.  What's the point of having a locally installed validator if it won't query a local web server?

The error message is: 

Sorry, the IP address of 192.168.1.111 is not public. For security reasons, validating resources located at non-public IP addresses has been disabled in this service.

The IP address of the machine hosting the validator was 192.168.1.99.  

Perhaps you should check to see if the validator and the IP address of the url being submitted are on the same subnet before throwing this error?

Where can I disable this check?
Comment 1 Olivier Thereaux 2007-01-20 00:34:54 UTC 
You probably just overwrote the configuration file when upgrading.
See validator.conf, and change
Allow Private IPs = no
to
Allow Private IPs = yes