Repository navigation
Replies: 1 comment 1 reply
|
The wildcard syntax is valid. The likely mismatch is the provider identifier: your log shows the display name In 3.8.52's matcher, exclusions are checked against the bare model ID and As a narrow diagnostic, add this line to the exclusions, save, reload the page to confirm it persisted, and make a new request: That excludes this model name across providers. To scope the exclusion to just your custom endpoint, use its full internal ID instead: Replace the placeholder with the actual ID; don't paste it literally. Historical log rows will keep their original compression figures. I ran the actual v3.8.52 matcher with your three patterns and the model/endpoint ID shown in the screenshots. The existing patterns did not match; the bare-model pattern and full endpoint-ID wildcard did. Case-insensitive matching and the literal dot in I haven't replayed your live request or checked your saved settings. If a fresh request still compresses with the bare-model exclusion saved, that would point to another issue beyond the identifier mismatch. |
Uh oh!
There was an error while loading. Please reload this page.
Hi community,
I've setup compression which works in general. But my exclusions seem not to work. Am I doing something wrong?
All reactions