fix: less restrictive assertion url inspection
Metadata
Current evaluation
Merged in #524 (commit 30a667f) and released in 0.11.1; assertion URLs are validated regardless of whether clients advertise assertion acceptance.
Resolution: closed resolved
Reason: PR #524 was approved with all CI checks passing and merged as commit 30a667f. The changelog lists the fix in fetch-service 0.11.1.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Recognize assertion URLs even if the client doesn't declare that it accepts
assertions. The validity of URL should be examined regardless of specific
client headers.
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged in #524 (commit 30a667f) and released in 0.11.1; assertion URLs are validated regardless of whether clients advertise assertion acceptance. | |
| stealth/space-bunny-alpha | — | closed resolved | PR #524 merged as commit 30a667f, making assertion URL validation independent of client accept-assertion headers. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged canonical/fetch-service#524 to recognize assertion URLs regardless of whether clients declare support for assertions. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #524 as commit 30a667f, making assertion URL inspection less restrictive by validating URLs regardless of client accept-assertion headers. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a fix to make assertion URL inspection less restrictive. The change recognizes assertion URLs regardless of client header declarations. Approved by two reviewers and passed all CI checks before merging. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.