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

http://tesco.com/groceries/ #4615

Closed
Closed

Description

@DanAtkinson

The Tesco Groceries site renders incorrectly in HTTP when the extension is enabled.

Disabling the extension allows the website to show correctly.

Activity

  1. MDawg957 commented on Apr 12, 2016

    @MDawg957

    Disabling the Tesco (partial) rule specifically should let it work till a proper fix can be implemented. The page loads correctly for me after I do that.

  2. DanAtkinson commented on Apr 12, 2016

    @DanAtkinson
    Author

    I have also reached out to Tesco separately, asking them to look at this problem.

    There's no logical reason why one of the largest supermarket chains in the world has an invalid SSL certificate on its homepage when loaded over HTTPS (https://www.tesco.com/).

    The SSL certificate is attributed to a248.e.akamai.net.

  3. J0WI commented on May 11, 2016

    @J0WI
    Contributor

    The sites CSP blocks content from secure.tesco.com

  4. added a commit that references this issue on May 28, 2016
    6fb69ab
  5. emberdart commented on Aug 18, 2016

    @emberdart

    I tried this partial one earlier on this week and got yet more issues from their site. I had to remove the whole site from consideration.

  6. DanAtkinson commented on Oct 8, 2016

    @DanAtkinson
    Author

    It is rather ridiculous that they can't support https everywhere across their servers and have instead created this situation for themselves where it's a mishmash of secure/insecure pages. It's not even consistent. I can be on http pages and have personal data exposed for no good reason.

  7. J0WI commented on Oct 9, 2016

    @J0WI
    Contributor

    There is a proposal for the CSP spec, that hard coded http:// policies should be ignored by browsers, but it has not been implemented yet.

  8. gerv commented on Nov 28, 2016

    @gerv

    This bug has been open six months; why not just remove the rule for Tesco from the HTTPSE ruleset, if it breaks things?

  9. rjgould commented on Dec 6, 2016

    @rjgould

    Have to agree with @gerv I couldn't figure out why Firefox wasn't showing the site properly so just had to play the "check every AddOn" game to find out it was HTTPS Everywhere. I'd rather this was excluded so I can go back to using the addon continuously instead of having to switch it on and off.

  10. J0WI commented on Feb 11, 2017

    @J0WI
    Contributor

    This ruleset depends on a lot of other ones, but since there are so many issues with that site I'm fine with just disabling it.

  11. galeksandrp commented on Apr 15, 2017

    @galeksandrp
    Contributor

    Did this issue persist?

  12. J0WI commented on Apr 16, 2017

    @J0WI
    Contributor

    https://secure.tesco.com/groceries/ looks broken, but https://www.tesco.com/groceries/ WFM

  13. janipewter commented on Apr 16, 2017

    @janipewter

    It does look like they have FINALLY fixed it

  14. Bisaloo commented on Feb 19, 2018

    @Bisaloo
    Collaborator

    Can we close this issue if this is fixed?

  15. DanAtkinson commented on Feb 19, 2018

    @DanAtkinson
    Author

    They appear to have fixed their hodge-podge SSL problems, so I believe that this issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions