Conversation
There was a problem hiding this comment.
Please also remove the corresponding <rule> below.
|
Yep, this ruleset is going to need a lot of Note that I had temporarily disabled ruleset coverage checking and forgot to turn it back on, which is why you haven't been seeing coverage errors for your branches so far. If you have the time to add the necessary coverage, that would be terrific. I would suggest taking the opportunity to simplify this ruleset a lot. This ruleset has been around for a long time, and in the meanwhile Google has greatly improved their HTTPS infrastructure and made HTTPS the default for a lot of situations. So for instance, the super long regex that lists the paths that work under HTTPS can probably be simplified to match just on hostnames. I am happy to assume that any path under www.google.* works on HTTPS today. If users report issues, we can add exceptions for specific paths. |
|
I'm still working on this, just wanted to push my changes to let others view them and see the build status. |
|
Looking good, thanks so much for working on this. By the way, if you'd like to be able to run the tests locally, and you have a Debian or Ubuntu machine, you can run |
249d913 to
cd1499e
Compare
…d one for complex rules
…overed by the default
|
hm.. I don't know why it's giving errors for |
|
I ran I'm a bit confused with some of the output:
http://api.recaptcha.net does work just 404s on / The majority of |
|
hm... might need some help getting the checker to work. `# git diff --name-only 28ec030 -- src | xargs ls | xargs python2.7 ~/https-everywhere-checker/src/https_everywhere_checker/check_rules.py ~/manual.conf``
|
|
That is odd, I'll take a look. |
|
It looks like you have a different version of https-everywhere-checker than I've been using. I recommend using it via Here are the current errors I get from this branch: Most of those are legit. I'll look into the 'NoneType' errors. |
Perhaps because it's an image file not html? |
|
I'm pretty sure that's not it. The tool doesn't try to parse the returned HTML at all. |
|
Other than the favicon thing (which I'll treat as spurious for now), what's the status of this branch? If it's close to ready I'd like to merge it for the upcoming release. |
|
It's at the review stage, I just need to review my rules. It's very close to being ready, few days? |
|
All my testing has been good. What the timeline for the 5.x (dev) releases? |
|
Great, thanks! It looks like like there are merge conflicts. Can you merge the latest master into your branch and then I will merge it? |
|
Interesting message: I didn't know this wasn't allowed in XML. It's easy to remove. |
|
FWIW, I was totally wrong about the 'xpath' error message. The checker does in fact parse the returned documents, to calculate Levenshtein distance of the tree structures. I'm working on a fix to the checker. There are still a few test URLs you added that get 200 without rewrite and 404 with rewrite. I'm fixing the relevant rule, then I'll manually merge. |
There was a problem hiding this comment.
FWIW, I'm guessing that using an incorrect version of https-everywhere-checker is why you are getting Travis test failures.
...e
Should I have written
<test>s for this?