Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 00:52
    javierguerragiraldez synchronize #4944
  • 00:52

    javierguerragiraldez on developers.md

    add automake stuff to install (compare)

  • 00:09
    p0pr0ck5 commented #4921
  • Aug 22 23:18
    jeremyjpj0916 commented #4949
  • Aug 22 23:03
    jeremyjpj0916 commented #4949
  • Aug 22 23:02
    jeremyjpj0916 commented #4949
  • Aug 22 23:02
    jeremyjpj0916 commented #4949
  • Aug 22 22:01
    jeremyjpj0916 commented #4949
  • Aug 22 22:00
    jeremyjpj0916 commented #4949
  • Aug 22 20:45
    jeremyjpj0916 commented #4949
  • Aug 22 20:44
    jeremyjpj0916 commented #4949
  • Aug 22 19:41

    bungle on router-update-frequency

    (compare)

  • Aug 22 19:38

    bungle on next

    feat(conf) add router_update_fr… (compare)

  • Aug 22 19:38
    bungle closed #4897
  • Aug 22 19:32
    mbugeia closed #3353
  • Aug 22 19:32
    mbugeia commented #3353
  • Aug 22 19:30
    bungle synchronize #4903
  • Aug 22 19:30

    bungle on plugins-iterator-cache-routes-and-services

    perf(proxy) cache plugins route… (compare)

  • Aug 22 18:49
    bungle synchronize #4926
  • Aug 22 18:49

    bungle on lyaml-6.2.4

    chore(deps) bump lyaml from 6.2… (compare)

zee.shen
@zeeshen
Besides, please take a look of this Kong/kong#4785 too. I think it's a reasonable one.
Rafael Gonzaga
@RafaelGSS
Hello! About this #667. Already in production ? I needs make the proxy to something:
/something/whatever to be routed to /routeJJ
Rafael Gonzaga
@RafaelGSS
LOL is 677 ISSUE, not PR : Kong/kong#677
mohammadreza kiani
@mkkia77_gitlab
hi there , i have a question about how to redirect all http request to https ? Can anyone help me please? and please note that i have successfully enabled my ssl certificate for kong and now the requests on http are working well
earllapura
@earllapura
Hi! Has anyone encountered the error No credentials found for given \'iss\'? I'm trying to get another service (in another VM) to connect to Kong. If I use the browser, I have no problem getting through using my JWT credentials. But when I'm using the service, I get this error. What could be the cause of this problem?
mohammadreza kiani
@mkkia77_gitlab
hi there , i'm using http_log plugin to send logs to a logstash server , but it's only work on a single node kong cluster , and other kong nodes doesn't send any log to logstash server, can anyone help me?
jeremyjpj0916
@jeremyjpj0916
@mkkia77_gitlab hard to draw any conclusion just based on that info. Do these Kong nodes leverage the same database, have you checked firewall rules and other things that might block the calls from the other kong node?
Simon Novak
@snovak7
Hello :) Can anyone help how can I install kong on macOS ?
openresty/1.15.8.1
could not find OpenResty 'nginx' executable. Kong requires version 1.13.6.2
so do I need exact version ?
Ramo Karahasan-Riechardt
@ramo-karahasan-riechardt
good evening
I'm using consul as service discovery where all my services are auto registered. Kong Services are equipped with consul dns names for services. I'm running a 3-node kong cluster with same postgres database. The confgiuration is pretty simple and not complicated. Currently I'm facing the issue that as soon as I create a service and a route and try to call this service endpoint, kong tells me that the name resolution failed. This goes even after one our of waiting. What helps is to reload kong. I'm wondering what the issue could be. The host machine where kong is running is configured using dnsmasq and dnsmasq basically to resolve dns queries via kong
Ramo Karahasan-Riechardt
@ramo-karahasan-riechardt
Sorry, it should be The host machine where kong is running is configured using dnsmasq and dnsmasq basically to resolve dns queries via consul
jmgpeeters
@jmgpeeters
I'm trying to use the response-transformer plugin to set the Vary header. I configure the return value to be ""Vary:Origin, X-Application-Key, Accept", but - when using this - the Vary header comes back as "Origin,X-Application-Key,Accept" (i.e. the whitespaces have been removed). is this intentional? I believe the spec requires the spaces to be included - but couldn't find any definitive source.
jmgpeeters
@jmgpeeters
also - is it possible to serve both HTTP and HTTPS over the same port (e.g. 8000)? or should they always be on different ports (e.g. 8000 and 8443)?
(to be clear - I don't want to redirect HTTP to HTTPS)
everfavio
@everfavio
Hi guys
does anyone know any way to register services and routes in kong from configuration files like yaml?
or another automatic way to register services/routes/plugins in kong
its possible?
jmgpeeters
@jmgpeeters
jeremyjpj0916
@jeremyjpj0916
Using a varient of the HTTP logger plugin we just ran into a interesting case where the logs seemed to be backfilling and the plugin seems to be hard set logging at 1 tps and falling behind in one of our environments. Might raise a git issue about it, I think we see in the code where the timer and delays are being done and if there might be ways to tune it to get better perf out of the logging functionality.
Anthony Morris
@amorriscode
Does anyone have a working example of tags?
curl -k -s https://localhost:9001/services/6f7d7016-bbdd-4229-a2a7-0f956a6583f0 -d "tags=example-tag" -XPATCH | jq
{
  "fields": {
    "tags": "unknown field"
  },
  "name": "schema violation",
  "code": 2,
  "message": "schema violation (tags: unknown field)"
}
jeremyjpj0916
@jeremyjpj0916
I just got on Kong 1.2.1 in prod so I have yet to play with tags, but will be doing so soon :), have a good use case for them in my head
I was doing a bit of reading and NGX should have a 2048 byte size limit, yet when I test like print() ngx.log() kong.log() all of them let me go beyond a 2048 size...
I didn't see any kong patches on openresty repo setting that static field greater than the 2048 ... but it seems more closer to 4096 bytes counting the pre + post apended gunk with any log.
Writing a little plugin might opensource to help with tx debugging to stdout, thats how I stumbled into the findings. Wish the buffer was overriden to allow like 10+ kb but I can always do some chunking :)
Aapo Talvensaari
@bungle

@jeremyjpj0916 could you please rebase : Kong/kong-plugin-zipkin#44

to resolve the conflict? I will be merging and releasing a new version with this.

jeremyjpj0916
@jeremyjpj0916
working on it, can confirm I suck at github xD. I have a few other PRs I been meaning to cook up too and clean up on rate limiting plugin and oauth2
jeremyjpj0916
@jeremyjpj0916
done, got something out there that should do the trick.
Thibault Charbonnier
@thibaultcha
@jeremyjpj0916 OpenResty patches the max error length to be 4096 instead of 2048
jeremyjpj0916
@jeremyjpj0916
@thibaultcha I gotcha, and thats something OpenResty themselves apply and Kong does not maintain it. Makes sense thats where the disconnect was for me because I was assuming Kong was doing it hah. Cool to know, thanks for the insight!
jeremyjpj0916
@jeremyjpj0916
Was reading here too: https://github.com/Kong/kong/blob/release/1.3.0/UPGRADE.md , few typos: (which puts the database in the final expected state for Kong 1.2) , should say 1.3 here.
maybe that is still WIP and known though!
Manuel Zago
@zagomanuel
hi, i have error: curl: (7) Failed to connect to kong port 8001: Operation timed out
Simon Novak
@snovak7
as you can see the app failed to respond in timely fashion (on port 8001)
or is not accessible due to network setup
filter action drop in firewalls
cedar715
@cedar715

Hi there, How to debug timeout errors in Kong? We are using Kong 1.20 Db-less deployed in Kube. For one client we are seeing 408, and for another client, ReadTimeOut is happening...

Client1 : 408 is seen in the access log
[20/Aug/2019:03:17:03 +0000]192.168.8.1 192.168.8.1 - POST HTTP/1.1 https /foo/bar/baz 408 60.000 0 - - - - Jakarta Commons-HttpClient/3.1 "Protocol of established connection:" TLSv1 "Cipher(s) used by client to establish connection:" AES128-SHA "List of ciphers supported by client:" 0x0004:0x0005:AES128-SHA:0x000a:0xfeff:TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Client2: No trace of request at Kong. But at their server logs, "Caused by: java.net.SocketTimeoutException: Read timed out" is recorded

these issues are happening intermittently..
jeremyjpj0916
@jeremyjpj0916
Hmm so there is an openresty-build-tools, which contains patches which seem relevant to recent http2 cve’s, and then there is the older openresty-patches that contain the bulk of patches Kong runs. Any reason these were broken out and not just having the patches in the openresty-patches repo like they all were before? So if I build from src now I need to hunt both repo’s for the regular patches and cve fixes? And will pulling both sets of nginx 1.15.8 patch sets cause any issues or is there an order I would need to execute the patch sets in from one repo to the next? My feeble brain can’t take all this thinking this am 🍳😂
jeremyjpj0916
@jeremyjpj0916
Actually no dilemma there the patches don’t clash with one another. Imma be a scrub and pick out the 1.15.8 cve’s and add them to the ones from the older repo in my docker build. All good 🤘
Thibault Charbonnier
@thibaultcha
openresty-build-tools should aim at producing a valid OpenResty installation, with (if necessary) bugfixes to NGINX/OpenResty as patches. Those patches are either because of edge case compilation issues or bugs that are worthy of a backported-patch. Essentially it only contains backported patches. However openresty-patches are new features for Kong itself or features that haven’t landed in OpenResty yet but that Kong needs. We’ve discussed merging patches, plus there’s the Kong Nginx module as well which is in another repository but should live closer to openresty-patches imho. All those deserve really good docs updates (btw we prepared a PR on the repository yesterday that should be up-to-date with the latest source/dev installation practices)
jeremyjpj0916
@jeremyjpj0916
:thumbsup: yeah I was able to wrap my head around it after noodling it some why its broken up a bit. I noticed in 1.3 the /kong_error_handler does not invoke the log_by_lua block anymore, was that intentional?
vs https://github.com/Kong/kong/blob/master/kong/templates/nginx_kong.lua#L174 , wondering how that will impact plugin logging that uses log_by_lua phase
for say 500 level errors, upstream timeout etc.
or was that able to be removed as redundancy because of the relocation of the phases above the location block that makes the proxy_pass call : https://github.com/Kong/kong/blob/release/1.3.0/kong/templates/nginx_kong.lua#L144 (figured it may be because of that).