{"message":"no Route matched with those values"}

Questions
9

What does this means . Is Kong redirecting to backend?

< X-Kong-Upstream-Latency: 0
< X-Kong-Proxy-Latency: 1

curl -v https://stg.com/

  • Trying 3.231.133.242:443…
  • TCP_NODELAY set
  • Connected to stg.com (x.x.x.x) port 443 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • successfully set certificate verify locations:
  • CAfile: /etc/ssl/certs/ca-certificates.crt
    CApath: /etc/ssl/certs
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  • ALPN, server accepted to use http/1.1
  • Server certificate:
  • subject: CN=stg.com
  • start date: Aug 22 19:27:23 2022 GMT
  • expire date: Nov 20 19:27:22 2022 GMT
  • subjectAltName: host “stg.com” matched cert’s “stg.com”
  • issuer: C=US; O=Let’s Encrypt; CN=R3
  • SSL certificate verify ok.

GET / HTTP/1.1
Host: stg.com
User-Agent: curl/7.68.0
Accept: /

  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • old SSL session ID is stale, removing
  • Mark bundle as not supporting multiuse
    < HTTP/1.1 200 OK
    < Content-Type: text/html; charset=UTF-8
    < Content-Length: 2022
    < Connection: keep-alive
    < Server: nginx/1.19.2
    < Date: Wed, 31 Aug 2022 18:52:51 GMT
    < Last-Modified: Thu, 18 Aug 2022 14:29:34 GMT
    < ETag: “62fe4cce-7e6”
    < Content-Security-Policy: upgrade-insecure-requests
    < Accept-Ranges: bytes
    < X-Kong-Upstream-Latency: 0
    < X-Kong-Proxy-Latency: 1
    < Via: kong/2.8.1
    <