-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Refine compliance and security documentation #22221
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
Refine compliance and security documentation #22221
Conversation
| ## Using Cloudflare's Services | ||
|
|
||
| Cloudflare launched in 2010 believing everyone deserves a secure, fast, reliable web presence. We did not think you should have to pay more when you came under cyber attack, so we offered free and fixed-rate pricing for websites. That worked because most websites don't consume much bandwidth, and so we could provide our services in an affordable way to everyone. From the beginning, we prohibited streaming video content using our bandwidth. While you could embed a video from another provider, we limited your ability to use our services to deliver video bits from our network to your visitors. This is because every second of a typical video requires as much bandwidth as loading a full web page. | ||
| This restriction exists because every second of a typical video requires as much bandwidth as loading a full web page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bllchmbrs, just flagging as another one.
Seems like there's ~1 big deletion per PR.
| ### Open ports versus blocked traffic | ||
|
|
||
| There is a difference between open ports and blocked traffic. Due to the nature of how Cloudflare’s anycast network works, ports other than 80 and 443 are always open so that Cloudflare can serve traffic for other customers on these ports. However, customers can easily block all unwanted traffic to these ports by using Cloudflare [WAF Managed Rules](/fundamentals/reference/network-ports/#how-to-block-traffic-on-additional-ports) or [custom rules](/waf/custom-rules/). The PCI scan will show the ports being open, but the traffic would not reach your origin server. This is an often misunderstood concern. | ||
| Cloudflare's anycast network operates in a way that keeps ports other than 80 and 443 open, allowing it to serve traffic for other customers on these ports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.... or multiple
...ntent/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx
Outdated
Show resolved
Hide resolved
…elivering-videos-with-cloudflare.mdx
src/content/docs/fundamentals/security/cloudflare-challenges/challenge-solve-issues.mdx
Outdated
Show resolved
Hide resolved
|
Congratulations @Hyperlint-AI[bot], the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmadzsg9318480djx76lpz48c This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
* Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Update src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx * Apply suggestions from code review --------- Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> Co-authored-by: Kody Jackson <[email protected]>
* Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Update src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx * Apply suggestions from code review --------- Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> Co-authored-by: Kody Jackson <[email protected]>
* Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Update src/content/docs/fundamentals/reference/policies-compliances/delivering-videos-with-cloudflare.mdx * Apply suggestions from code review --------- Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> Co-authored-by: Kody Jackson <[email protected]>
This pull request addresses various style guide compliance issues across multiple documentation files. The changes primarily focus on correcting non-standard quotes, removing contractions, clarifying unclear antecedents, and eliminating end-of-line whitespace. Additionally, some repetitive phrases were removed, and punctuation in headings was adjusted to meet the style guide requirements.
cloudflare-cookies.mdx,cybersafe.mdx,delivering-videos-with-cloudflare.mdx,pci-scans.mdx,subscriptions-and-billing/preview-services.mdx)scim-setup.mdx,under-ddos-attack.mdx,subscriptions-and-billing/cancel-subscription.mdx)