-
Notifications
You must be signed in to change notification settings - Fork 1.1k
http://tesco.com/groceries/ #4615
Comments
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. |
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. |
The sites CSP blocks content from secure.tesco.com |
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. |
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. |
There is a proposal for the CSP spec, that hard coded |
This bug has been open six months; why not just remove the rule for Tesco from the HTTPSE ruleset, if it breaks things? |
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. |
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. |
Did this issue persist? |
|
It does look like they have FINALLY fixed it |
Can we close this issue if this is fixed? |
They appear to have fixed their hodge-podge SSL problems, so I believe that this issue can be closed. |
The Tesco Groceries site renders incorrectly in HTTP when the extension is enabled.
Disabling the extension allows the website to show correctly.
The text was updated successfully, but these errors were encountered: