kong
Here are 381 public repositories matching this topic...
Summary
It's annoying to remember the right protobuf structure for envoy socket address. There is a helper in pkg/envoy/accesslog/v3/helper_test.go that wraps the boilerplate.
We should move this to a regular util package and use it everywhere.
-
Updated
Oct 22, 2020 - JavaScript
A Kong SNI can only point to a single certificate. Per Kong/kubernetes-ingress-controller#1268 (comment), misconfigured Kubernetes resources can attempt to point an SNI to multiple certificates.
While we do avoid adding attached SNIs to new certificates, we do
-
Updated
Sep 7, 2021
-
Updated
Aug 24, 2021 - JavaScript
-
Updated
Jul 5, 2021
-
Updated
Aug 9, 2020 - JavaScript
-
Updated
Sep 10, 2021 - Go
-
Updated
Aug 12, 2021 - JavaScript
-
Updated
Apr 19, 2018 - Go
-
Updated
Jul 6, 2021 - PHP
-
Updated
Sep 10, 2019
-
Updated
Apr 17, 2019 - Lua
-
Updated
Sep 10, 2021 - Lua
-
Updated
Mar 13, 2019 - Java
-
Updated
Sep 6, 2021 - Lua
-
Updated
May 19, 2020 - JavaScript
-
Updated
Dec 3, 2020
-
Updated
Dec 28, 2020 - HTML
-
Updated
Dec 22, 2020 - Java
-
Updated
Jul 7, 2021
-
Updated
Aug 4, 2021 - Lua
Improve this page
Add a description, image, and links to the kong topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the kong topic, visit your repo's landing page and select "manage topics."
Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.
{ "error_description": "You must use HTTPS", "error": "access_denied" }I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.