-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ghostery breaks onBeforeRequest redirects made by other extensions #44
Labels
Bug
Something isn't working
Comments
lidel
changed the title
Ghostery breaks webRequest.onBeforeRequest made by other extensions
Ghostery breaks onBeforeRequest redirects made by other extensions
Apr 22, 2018
This is most likely coming from Smart Block checking for mixed content. See PolicySmartBlock.js We had another issue recently where this was breaking SQRL login for the same reason. We need to add a check and allow mixed content from |
Yup, |
christophertino
added a commit
that referenced
this issue
Jul 6, 2018
christophertino
pushed a commit
that referenced
this issue
Mar 17, 2021
…-2305) (#675) * Expand toggle and select plus plan if user is basic and selects ghostery search * Make ghostery glow icon bigger in select default search modal * Move ghostery logo on search option selection container a little to the left * Remove expansion by default * Update logo sizes on choose default search view * Adjust sizing for Yahoo, Startpage, and Bing logos in search selection modals to better match Zeplins * Increase chance user object is available before choose plan view render. Show expanded view if user picked Glow to match expected UX. Add TODOs so we remember to update AccountReducer to help distinguish between no user present and user not fetched yet * Factor out option card checkmark item rendering to a helper to reduce duplication. * Update test snapshots * Refactor choose plan view plan card feature copy rendering to a helper to reduce duplication * Factor user status checks in select plan view out to helpers to reduce duplication and bug surface * Move setting of default plan in plan select view to componentDidMount to avoid using setTimeout to setState in constructor * Revised setDefaultPlan() logic in ChoosePlanView to make sure everything renders as expected when user is Plus or Premium Co-authored-by: wlycdgr <ilya.zarembsky@gmail.com>
chrmod
added a commit
that referenced
this issue
Jul 28, 2022
`onBeforeNaviagate` denotes that start of the transition chain, while `onCommitted` is bound to the document livecycle. `onCommitted` should also fire on cold starts.
chrmod
pushed a commit
that referenced
this issue
Jul 28, 2022
chrmod
pushed a commit
that referenced
this issue
Jul 28, 2022
chrmod
pushed a commit
that referenced
this issue
Jul 28, 2022
…-2305) (#675) * Expand toggle and select plus plan if user is basic and selects ghostery search * Make ghostery glow icon bigger in select default search modal * Move ghostery logo on search option selection container a little to the left * Remove expansion by default * Update logo sizes on choose default search view * Adjust sizing for Yahoo, Startpage, and Bing logos in search selection modals to better match Zeplins * Increase chance user object is available before choose plan view render. Show expanded view if user picked Glow to match expected UX. Add TODOs so we remember to update AccountReducer to help distinguish between no user present and user not fetched yet * Factor out option card checkmark item rendering to a helper to reduce duplication. * Update test snapshots * Refactor choose plan view plan card feature copy rendering to a helper to reduce duplication * Factor user status checks in select plan view out to helpers to reduce duplication and bug surface * Move setting of default plan in plan select view to componentDidMount to avoid using setTimeout to setState in constructor * Revised setDefaultPlan() logic in ChoosePlanView to make sure everything renders as expected when user is Plus or Premium Co-authored-by: wlycdgr <ilya.zarembsky@gmail.com>
chrmod
added a commit
that referenced
this issue
Jul 28, 2022
`onBeforeNaviagate` denotes that start of the transition chain, while `onCommitted` is bound to the document livecycle. `onCommitted` should also fire on cold starts.
chrmod
pushed a commit
that referenced
this issue
Jul 29, 2022
chrmod
pushed a commit
that referenced
this issue
Jul 29, 2022
chrmod
pushed a commit
that referenced
this issue
Jul 29, 2022
…-2305) (#675) * Expand toggle and select plus plan if user is basic and selects ghostery search * Make ghostery glow icon bigger in select default search modal * Move ghostery logo on search option selection container a little to the left * Remove expansion by default * Update logo sizes on choose default search view * Adjust sizing for Yahoo, Startpage, and Bing logos in search selection modals to better match Zeplins * Increase chance user object is available before choose plan view render. Show expanded view if user picked Glow to match expected UX. Add TODOs so we remember to update AccountReducer to help distinguish between no user present and user not fetched yet * Factor out option card checkmark item rendering to a helper to reduce duplication. * Update test snapshots * Refactor choose plan view plan card feature copy rendering to a helper to reduce duplication * Factor user status checks in select plan view out to helpers to reduce duplication and bug surface * Move setting of default plan in plan select view to componentDidMount to avoid using setTimeout to setState in constructor * Revised setDefaultPlan() logic in ChoosePlanView to make sure everything renders as expected when user is Plus or Premium Co-authored-by: wlycdgr <ilya.zarembsky@gmail.com>
chrmod
added a commit
that referenced
this issue
Jul 29, 2022
`onBeforeNaviagate` denotes that start of the transition chain, while `onCommitted` is bound to the document livecycle. `onCommitted` should also fire on cold starts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
IPFS Companion is a browser extension that enables users to detect content-addressed resources on websites and redirect them to a local IPFS2HTTP gateway (localhost or LAN).
It seems that when Ghostery is enabled and user loads a HTTPS website with content-addressed IPFS resources, Ghostery breaks the gateway redirect by forcing HTTPS even if user chose to use a localhost or LAN gateway exposed on HTTP.
More details: ipfs/ipfs-companion#466
Expected Behavior
Ghostery should detect and respect internal redirects (HTTP 307) made by other extensions.
Note that HTTPS Everywhere does not break the same website.
Actual Behavior
Ghostery always upgrades URL of HTTP 307 to HTTPS, breaking IPFS websites:
Steps to Reproduce
https://
instead of redirectedhttp://
(like in this screenshot)Versions
The text was updated successfully, but these errors were encountered: