nfrankel commented on code in PR #1495: URL: https://github.com/apache/apisix-website/pull/1495#discussion_r1101524308
########## blog/en/blog/2023/02/09/secure-apisix-admin.md: ########## @@ -0,0 +1,151 @@ +--- +title: Securing Admin access to Apache APISIX +authors: + - name: Nicolas Fränkel + title: Author + url: https://github.com/nfrankel + image_url: https://avatars.githubusercontent.com/u/752258 +keywords: + - Security + - Admin API +description: > + API Gateways are critical components in one's infrastructure. If an attacker could change the configuration of routes, they could direct traffic to their infrastructure. Consequences could range from data theft to financial losses. Worse, data theft could only be noticed after a long time by mirroring the load. Hence, protecting your API Gateway is of utmost importance Review Comment: >for SEO because no more than 120 characters would be better. That's what we have done since Q4 last year. It works I'm sorry but that's not how it works. To prove that the proposal works, you should do A/B testing with the exact same content and only the description changed. Then, you'd measure and validate your claim - or not. I'll repeat what I wrote above: >Most SEO is based on assumptions only because Google keeps his algorithm secret to avoid people gaming it. I'll abide by your proposal if you insist, but please don't make allegations that cannot be proven. My experience with SEO is that it's [snake oil](https://en.wiktionary.org/wiki/snake_oil) wrapped in big words and backed by nothing but hearsay. Here's the **only** guide that you can trust: [Search Engine Optimization (SEO) Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide). As you can see, it's very succinct and doesn't tell anything regarding the description. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
