Functional Description

AI History Dialogue implements user identity recognition based on request headers and automatically caches the historical dialogues of corresponding users, which are then automatically filled into the context in subsequent dialogues. It also supports users to actively query historical dialogues.

Note

When the path suffix matches ai-history/query, it will return the historical dialogues.

Runtime Properties

Plugin Execution Phase: Default Phase Plugin Execution Priority: 650

Configuration Fields

NameData TypeRequiredDefault ValueDescription
identityHeaderstringoptional”Authorization”The request header for identity resolution, can be Authorization, X-Mse-Consumer, etc.
fillHistoryCntintegeroptional3Default number of historical dialogues to be filled.
cacheKeyPrefixstringoptional”higress-ai-history:“Prefix for Redis cache key.
cacheTTLintegeroptional0Cache expiration time in seconds, default value is 0, meaning it never expires.
redis.serviceNamestringrequired-Redis service name, full FQDN name with service type, e.g., my-redis.dns, redis.my-ns.svc.cluster.local
redis.servicePortintegeroptional6379Redis service port.
redis.timeoutintegeroptional1000Timeout for requests to Redis, in milliseconds.
redis.usernamestringoptional-Username for logging into Redis.
redis.passwordstringoptional-Password for logging into Redis.

Usage Example

Configuration Information

  1. redis:
  2.   serviceName: my-redis.dns
  3.   timeout: 2000

Request Example

Auto-fill Request Example:

First Round Request:

  2.   -H ‘Accept: application/json, text/event-stream’ \
  3.   -H ‘Content-Type: application/json’ \
  4.   -H ‘Authorization: Bearer sk-Nzf7RtkdS4s0zFyn5575124129254d9bAf9473A5D7D06dD3’
  5.   —data-raw ‘{“model”:”qwen-long”,”frequency_penalty”:0,”max_tokens”:800,”stream”:false,”messages”:[
  6.         {
  7.             “role”: “user”,
  8.             “content”: “Can Higress replace Nginx?”
  9.         }
  10.     ],”presence_penalty”:0,”temperature”:0.7,”top_p”:0.95}’

After Request Fill:

First round request, no fill. Consistent with the original request.

First Round Response:

  1. {
  2.   “id”: “02f4c621-820e-97d4-a905-1e3d0d8f59c6”,
  3.   “choices”: [
  4.     {
  5.       “index”: 0,
  6.       “message”: {
  7.         “role”: “assistant”,
  8.         “content”: “While both Higress and Nginx have gateway functionalities, their design philosophies and application scenarios differ. Nginx is better known as a high-performance HTTP and reverse proxy server, while Higress is a cloud-native gateway that integrates many cloud-native features such as service mesh, observability, and security management in addition to basic routing capabilities.\n\nTherefore, if you want to deploy applications in a cloud-native environment and wish to obtain advanced features required for modern applications, such as service governance, gray release, circuit breaker and rate limiting, and security authentication, then Higress can be a good alternative to Nginx. However, if it’s a relatively simple static website or only requires basic reverse proxy functionality, traditional Nginx configurations may be simpler and more direct.”
  9.       },
  10.       “finish_reason”: “stop”
  11.     }
  12.   ],
  13.   “created”: 1724077770,
  14.   “model”: “qwen-long”,
  15.   “object”: “chat.completion”,
  16.   “usage”: {
  17.     “prompt_tokens”: 7316,
  18.     “completion_tokens”: 164,
  19.     “total_tokens”: 7480
  20.   }
  21. }

Second Round Request:

  2.   -H ‘Accept: application/json, text/event-stream’ \
  3.   -H ‘Content-Type: application/json’ \
  4.   -H ‘Authorization: Bearer sk-Nzf7RtkdS4s0zFyn5575124129254d9bAf9473A5D7D06dD3’
  5.   —data-raw ‘{“model”:”qwen-long”,”frequency_penalty”:0,”max_tokens”:800,”stream”:false,”messages”:[
  6.         {
  7.             “role”: “user”,
  8.             “content”: “What about Spring Cloud GateWay?”
  9.         }
  10.     ],”presence_penalty”:0,”temperature”:0.7,”top_p”:0.95}’

After Request Fill:

Second round request, automatically filled with the historical dialogue from the previous round.

  2.   -H ‘Accept: application/json, text/event-stream’ \
  3.   -H ‘Content-Type: application/json’ \
  4.   -H ‘Authorization: Bearer sk-Nzf7RtkdS4s0zFyn5575124129254d9bAf9473A5D7D06dD3’
  5.   —data-raw ‘{“model”:”qwen-long”,”frequency_penalty”:0,”max_tokens”:800,”stream”:false,”messages”:[
  6.          {
  7.             “role”: “user”,
  8.             “content”: “Can Higress replace Nginx?”
  9.         },
  10.         {
  11.             “role”: “assistant”,
  12.             “content”: “While both Higress and Nginx have gateway functionalities, their design philosophies and application scenarios differ. Nginx is better known as a high-performance HTTP and reverse proxy server, while Higress is a cloud-native gateway that integrates many cloud-native features such as service mesh, observability, and security management in addition to basic routing capabilities.\n\nTherefore, if you want to deploy applications in a cloud-native environment and wish to obtain advanced features required for modern applications, such as service governance, gray release, circuit breaker and rate limiting, and security authentication, then Higress can be a good alternative to Nginx. However, if it’s a relatively simple static website or only requires basic reverse proxy functionality, traditional Nginx configurations may be simpler and more direct.”
  13.         },
  14.         {
  15.             “role”: “user”,
  16.             “content”: “What about Spring Cloud GateWay?”
  17.         }
  18.     ],”presence_penalty”:0,”temperature”:0.7,”top_p”:0.95}’

Each round of requests only needs to include the current question and the number of historical dialogues to fill in, enabling automatic filling of historical dialogues.

Example of Retrieving Historical Data:

  2.   -H ‘Accept: application/json, text/event-stream’ \
  3.   -H ‘Content-Type: application/json’ \
  4.   -H ‘Authorization: Bearer sk-Nzf7RtkdS4s0zFyn5575124129254d9bAf9473A5D7D06dD3’

Response Example:

  1. [
  2.   {
  3.     “role”: “user”,
  4.     “content”: “Can Higress replace Nginx?”
  5.   },
  6.   {
  7.     “role”: “assistant”,
  8.     “content”: “While both Higress and Nginx have gateway functionalities, their design philosophies and application scenarios differ. Nginx is better known as a high-performance HTTP and reverse proxy server, while Higress is a cloud-native gateway that integrates many cloud-native features such as service mesh, observability, and security management in addition to basic routing capabilities.\n\nTherefore, if you want to deploy applications in a cloud-native environment and wish to obtain advanced features required for modern applications, such as service governance, gray release, circuit breaker and rate limiting, and security authentication, then Higress can be a good alternative to Nginx. However, if it’s a relatively simple static website or only requires basic reverse proxy functionality, traditional Nginx configurations may be simpler and more direct.”
  9.   },
  10.   {
  11.     “role”: “user”,
  12.     “content”: “What about Spring Cloud GateWay?”
  13.   },
  14.   {
  15.     “role”: “assistant”,
  16.     “content”: “Compared to Spring Cloud Gateway, Higress is also an API gateway, but there are some key differences between them:\n\n- Design Philosophy: Spring Cloud Gateway mainly targets service-to-service communication and routing in microservice architectures. As part of the Spring Cloud ecosystem, it is more focused on scenarios for Java developers in microservices. In contrast, Higress, as a cloud-native gateway, not only focuses on service communication but also offers a range of cloud-native features such as service mesh, observability, security management, etc.\n- Deployment Method: Spring Cloud Gateway typically runs as part of microservice applications on application servers, whereas Higress usually deploys as an independent microservice or containerized service in Kubernetes environments, suitable for modern cloud-native deployment models.\n- Scalability and Integration: Higress provides wider integration and support, for example, deep integration with ecosystems like Istio, Kubernetes, etc., making it better suited for complex cloud-native environments.\n\nTherefore, if your application is built on Spring Cloud and you want a lightweight, easy-to-integrate service gateway, then Spring Cloud Gateway might be a suitable choice. However, if you are building or refactoring cloud-native applications and require more powerful routing rules, service governance, observability, etc., then Higress is likely a better choice.”
  17.   },
  18.   {
  19.     “role”: “user”,
  20.     “content”: “Can Higress replace Nginx?”
  21.   },
  22.   {
  23.     “role”: “assistant”,
  24.     “content”: “While both Higress and Nginx have gateway functionalities, their design philosophies and application scenarios differ. Nginx is better known as a high-performance HTTP and reverse proxy server, while Higress is a cloud-native gateway that integrates many cloud-native features such as service mesh, observability, and security management in addition to basic routing capabilities.\n\nTherefore, if you want to deploy applications in a cloud-native environment and wish to obtain advanced features required for modern applications, such as service governance, gray release, circuit breaker and rate limiting, and security authentication, then Higress can be a good alternative to Nginx. However, if it’s a relatively simple static website or only requires basic reverse proxy functionality, traditional Nginx configurations may be simpler and more direct.”
  25.   }
  26. ]

Returns three historical dialogues. If the cnt parameter is not provided, it will default to returning all cached historical dialogues.