Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow certain 40x responses when testing rulesets #17064
Comments
J0WI
added
the
ruleset-testing
label
Dec 3, 2018
This comment has been minimized.
This comment has been minimized.
|
ad.dmm.com and ad.dmm.co.jp also require exact path for ads or it returns 403. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
fghzxm commentedNov 14, 2018
•
edited
Type: code issue
The ruleset tester only accepts a target host if an HTTPS request to the host is responded with HTTP 20x. It may be a good idea to accept HTTP 401, 403 and like as well.
For example, websites like
demos.igalia.comrequire HTTP authentication for access. Such hosts are currently rejected by the ruleset tester because they respond with HTTP 401 rather than 20x.However, in reality users of those websites will submit credentials and be able to browse them. Due to the nature of such websites it is even more important to have proactive HTTPS protection for them than for publicly accessible websites.