Bug: In the case of k8s deployment, the url suffix cannot be parsed

[yisany]

Chat2DB Version

3.1.19

Describe the bug

I deploy chat2db in a k8s cluster, mirror version:chat2db/chat2db:3.1.19

Ingress is used to provide access. The ideal url is:

http://myhost.com/ide-db

The specific configuration of Ingress is as follows:

---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: chat2db
  namespace: default
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/proxy-body-size: "100M"
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "300s"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "300s"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "300s"
spec:
  rules:
    - http:
        paths:
          - backend:
              service:
                name: chat2db
                port:
                  number: 10824
            path: /ide-db(/|$)(.*)
            pathType: ImplementationSpecific

But after I configured it like this, I found that it didn't work after accessing it. All api requests would ignore the first-layer path I configured.

#Ideal request path
http://myhost.com/ide-db/login?callback=/
# Actual request path
http://myhost.com/login?callback=/

Currently, there is no condition to provide a second-level domain name. We can only use the url suffix method. We hope this function can be supported.

[mapleTan1113]

hi bro, i ran into the same issue, did u fix it?