Skip to content
This repository has been archived by the owner on Nov 6, 2023. It is now read-only.

Re-activate and Update Alltop.com.xml #9862

Merged
merged 1 commit into from May 19, 2017
Merged

Re-activate and Update Alltop.com.xml #9862

merged 1 commit into from May 19, 2017

Conversation

cschanaj
Copy link
Collaborator

@cschanaj cschanaj commented May 9, 2017

Related: #9842

-->
<ruleset name="AllTop.com">
<target host="alltop.com" />
<target host="*.alltop.com" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there also a reason to use a wildcard target or can we list all hosts?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wildcard DNS basically redirect https://foo.alltop.com to http://alltop.com/?keywords=foo. And there is 700+ sub-domain support HTTPS correctly. I do not want this to overwhelm reviewers and future maintainers. If you prefer, I can rebase it.

See https://gist.github.com/cschanaj/f0fdfa8f0535ded83603b1dfe1827b4e (Only checked automatically).

@J0WI J0WI merged commit e4b2b6a into EFForg:master May 19, 2017
@cschanaj cschanaj deleted the cschanaj-alltop.com branch May 20, 2017 01:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants