Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Create ruleset: Elgas.com.au#15772

Merged
J0WI merged 3 commits into
EFForg:masterEFForg/https-everywhere:masterfrom
injust:patch-217Copy head branch name to clipboard
Jun 28, 2018
Merged

Create ruleset: Elgas.com.au#15772
J0WI merged 3 commits into
EFForg:masterEFForg/https-everywhere:masterfrom
injust:patch-217Copy head branch name to clipboard

Conversation

@injust

@injust injust commented Jun 16, 2018

Copy link
Copy Markdown
Contributor

No description provided.

@Hainish Hainish added the top-1m label Jun 16, 2018
<ruleset name="Elgas.com.au">
<target host="elgas.com.au" />
<target host="www.elgas.com.au" />
<target host="emap.elgas.com.au" />

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

secure.elgas.com.au

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

That host fails the CI build, because accessing it on HTTP redirects to www.secure.elgas.com.au, which DNE.
Maybe the Travis tests should be modified to allow for sites that only work on HTTPS?

@J0WI J0WI Jun 17, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The problem here is that HTTP serves a different response than HTTPS. Could you document the issue?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I've added a comment for secure.elgas.com.au.
In this case, would it be better to leave the target out of the ruleset, or include it and whitelist the ruleset against fetch tests?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I don't know what the expected behavior would be in this case. I'm fine with both variants.

@J0WI J0WI merged commit c5d7c69 into EFForg:master Jun 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.