higress icon indicating copy to clipboard operation
higress copied to clipboard

🤖 AI Gateway | AI Native API Gateway

Results 337 higress issues
Sort by recently updated
recently updated
newest added

**If you are reporting *any* crash or *any* potential security issue, *do not* open an issue in this repo. Please report the issue via [ASRC](https://security.alibaba.com/)(Alibaba Security Response Center) where the...

## Why do you need it? 前端灰度的插件对接CDN的部署方式,需要用户托管首页HTML,但是一般的情况下,CDN只是存储相关的`js/css/images`等静态的资源。需要能够托管HTML首页。 ## How could it be? ``` html: |- MFE 微前端应用: App1 MFE 微前端应用: App1 ``` ## Other related information 如果 `html`字段存在,则 `rewrite.indexRouting`则无效

level/challenge
sig/wasm

## proxy-wasm-rust-sdk - 讨论 sdk 中不安全的unwrap()和panic是否需要修改为安全 - 上游的panic理论上都是不该出现的情况 https://github.com/proxy-wasm/proxy-wasm-rust-sdk/pull/83 https://github.com/proxy-wasm/proxy-wasm-rust-sdk/pull/82 - 部分错误应该在上游修改 https://github.com/proxy-wasm/proxy-wasm-rust-sdk/pull/217 https://github.com/proxy-wasm/proxy-wasm-rust-sdk/pull/188 - plugin_wrapper中目前`create_heep_context`需要使用者主动效用`create_heep_context_use_wrapper`,讨论是否需要少量改动sdk来让使用者更方便 ## higress wasm-rust sdk | 功能模块 | 难度 | 完成情况 | | ------------------ |...

level/challenge
sig/wasm

### Ⅰ. Describe what this PR did 1. 增加按照比例灰度的能力,YAML配置如下: 灰度规则 `beta-user`的灰度范围为 50% ``` baseDeployment: version: "dev" grayDeployments: - name: "beta-user" version: "0.0.1" enabled: "true" weight: "50" ``` 2. 添加往首页注入脚本的能力 可以分别在...

更新内容安全插件: - 配置更新:用户可以选择只在request/response阶段检测,或者都检测。如果被内容安全拦截,根据请求是否为流式返回流式/非流式响应。如果response阶段进行检测,虽然响应是流式的,但是需要缓存所有的chunk提取大模型的完整回答进行检测,所以在前端页面上表现为非流式。 - 增加metrics以及span attributes供用户排查问题使用。

### Ⅰ. Describe what this PR did This PR extends the functionality of the `ai-cache` plugin, enabling more efficient AI application development by introducing vector similarity-based caching and recall mechanisms....

### Ⅰ. Describe what this PR did 配置示例: ```yaml provider: type: qwen apiTokens: - "api-token-1" - "api-token-2" - "api-token-3" modelMapping: 'gpt-3': "qwen-turbo" 'gpt-4-turbo': "qwen-max" '*': "qwen-turbo" failover: enabled: true failureThreshold:...

如图,配置了基于该域名层级的黑名单url,测试无效 ![image](https://github.com/user-attachments/assets/905f0867-1d97-42c3-bdda-9369ae814300) ![image](https://github.com/user-attachments/assets/62b50b19-c675-4be1-8002-e459f020a722)

![6d790505ba40d84dd325bc878f348f11](https://github.com/user-attachments/assets/4e0ef1c0-0555-49c8-afcf-c697915575a1) 1、能否跟ingress-nginx一样,单条域名在设置多个路由规则转发到不同的后端服务?现在web里面只能配置一个。在k8s里面就会产生2个文件,看起来很不舒服。 2、同时如果配置了相同的host,2个路由时,在删除其中一个的时候,会干掉2个路由规则。你们可以测试这应该是bug。