On Tue, May 21, 2019 at 11:01 AM <wr...@apache.org> wrote: > Author: wrowe > Date: Tue May 21 16:00:46 2019 > New Revision: 1859658 > > URL: http://svn.apache.org/viewvc?rev=1859658&view=rev > Log: > s/http:/https:/ - note that usefulinc.com is not so useful, cert CN > mismatch > > --- apr/site/trunk/doap.rdf (original) > +++ apr/site/trunk/doap.rdf Tue May 21 16:00:46 2019 > @@ -1,16 +1,16 @@ > <?xml version="1.0"?> > <rdf:RDF xmlns="http://usefulinc.com/ns/doap#"; > - xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; > - xmlns:asfext="http://projects.apache.org/ns/asfext#"; xml:lang="en"> > + xmlns:rdf="https://www.w3.org/1999/02/22-rdf-syntax-ns#"; > + xmlns:asfext="https://projects.apache.org/ns/asfext#"; xml:lang="en"> > ...
While all the other elts could be mapped to https:, usefulinc.com presents simonstl.com as the site cert CN, and further has the wrong media encoding for http://usefulinc.com/ns/doap# (it presents utf-8 while claiming iso-8859-1). What would be the suggested way to handle these discrepancies? For a standard, they don't appear to grok standards.
