changed prefer strategy for http unique in such a way that http is

preferred over https. While this is a bad idea from the standpoint of
security it is more common applicable for environments where http and
https mix and for some domains https is not available. Then the
double-check is possible even if no postprocessing is performed.
pull/1/head
Michael Peter Christen 10 years ago
parent 84e2cccab4
commit eb78388a98

@ -1033,7 +1033,7 @@ search.ranking.solr.doubledetection.quantrate=0.5f
# Another attribute for double content is a 'greedy' ignoring of a http url is present for each https and vice versa
# The same may be true for documents with leading 'www.' subdomain and without.
# The following attributes will cause that https is preferred over http and with-www is preferred over without-www
search.ranking.uniqueheuristic.preferhttps = true
search.ranking.uniqueheuristic.preferhttps = false
search.ranking.uniqueheuristic.preferwwwprefix = true
#optional extern thumbnail program.

@ -373,7 +373,7 @@ public final class Switchboard extends serverSwitch {
SwitchboardConstants.DICTIONARY_SOURCE_PATH_DEFAULT);
this.log.config("Dictionaries Path:" + this.dictionariesPath.toString());
CollectionConfiguration.UNIQUE_HEURISTIC_PREFER_HTTPS = this.getConfigBool("search.ranking.uniqueheuristic.preferhttps", true);
CollectionConfiguration.UNIQUE_HEURISTIC_PREFER_HTTPS = this.getConfigBool("search.ranking.uniqueheuristic.preferhttps", false);
CollectionConfiguration.UNIQUE_HEURISTIC_PREFER_WWWPREFIX = this.getConfigBool("search.ranking.uniqueheuristic.preferwwwprefix", true);

@ -108,7 +108,7 @@ public class CollectionConfiguration extends SchemaConfiguration implements Seri
private static final long serialVersionUID=-499100932212840385L;
public static boolean UNIQUE_HEURISTIC_PREFER_HTTPS = true;
public static boolean UNIQUE_HEURISTIC_PREFER_HTTPS = false;
public static boolean UNIQUE_HEURISTIC_PREFER_WWWPREFIX = true;
private final ArrayList<Ranking> rankings;

Loading…
Cancel
Save