Buy European
Overview:
The community to discuss buying European goods and services.
Rules:
-
Be kind to each other, and argue in good faith. No direct insults nor disrespectful and condescending comments.
-
Do not use this community to promote Nationalism/Euronationalism. This community is for discussing European products/services and news related to that. For other topics the following might be of interest:
-
Include a disclaimer at the bottom of the post if you're affiliated with the recommendation.
Feddit.uk's instance rules apply:
- No racism, sexism, homophobia, transphobia or xenophobia
- No incitement of violence or promotion of violent ideologies
- No harassment, dogpiling or doxxing of other users
- Do not share intentionally false or misleading information
- Do not spam or abuse network features.
- Alt accounts are permitted, but all accounts must list each other in their bios.
Benefits of Buying Local:
local investment, job creation, innovation, increased competition, more redundancy.
Related Communities:
Buy Local:
Buying and Selling:
!flohmarkt@lemmy.ca
Boycott:
!boycottus@lemmy.ca
Stop Publisher Kill Switch in Games Practice:
!stopkillinggames@lemm.ee
Banner credits: BYTEAlliance
view the rest of the comments
You see the problem. Yes, cloudflare decrypt the request from the browser, inspect it, then reencrypt it and send it to the host server. Then they take the response, decrypt that, inspect it, reencrypt it and send it to the browser.
Basically there are two TLS flows, one from the browser to cloudflare, and one from clourflare to the host server. Between those, on the cloudflare system, both the traffic and response are in plain text. That includes usernames, passwords (for HTTP basic auth anyway) and any sensitive data you send or receive.
Given that they front sonewhere between 19 and 40% of all websites, d£pending on whose stats you trust, that should be pretty alarming.
Thank you. I didn't know that.