fix(console): restore admin_auth_cors_ratelimit test after ureq 3 API drift (task #37)

[pilotspacex-byte]

What

Task #37: the console-feature test admin_auth_cors_ratelimit was written against ureq 2.x but Cargo.toml pins ureq = "3" (Lock: 3.3.0). ureq 3 renamed/removed .set(), .timeout(), ureq::request(), resp.header(), and — the breaking part — ureq::Error::StatusCode(u16) no longer carries the Response, so header assertions on 4xx/5xx (www-authenticate on 401, retry-after on 429) were structurally unreachable.

Fix

Two helpers build each request with .config().http_status_as_error(false).timeout_global(...).build(), so 4xx/5xx come back as Ok(Response) and the test asserts on resp.status()/resp.headers() directly. Every original assertion preserved (bearer enforcement, tampered-signature rejection, CORS origin echo/elision, 429 + retry-after, preflight bypass, healthz/readyz auth exemption). Test-only change; no non-test console code used ureq.

Verification

• cargo test --release --features console --test admin_auth_cors_ratelimit → 7/7
• cargo fmt --check clean; cargo clippy --no-default-features --features runtime-monoio,jemalloc,graph,text-index,console --tests -D warnings clean (matches CI check-console exactly)

Summary by CodeRabbit

• Tests
  • Improved coverage and reliability for authentication, CORS, rate-limiting, health-check, and metrics response handling.
  • Tests now directly verify HTTP status codes and headers for both successful and error responses.
  • Updated startup health-check polling with more efficient response handling and timeouts.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 13c4451c-a6fc-4958-964c-23095f744b65

📥 Commits

Reviewing files that changed from the base of the PR and between f6518c5 and 5f1f423.

📒 Files selected for processing (1)

• tests/admin_auth_cors_ratelimit.rs

---

📝 Walkthrough

Walkthrough

Changes

HTTP response handling tests

Layer / File(s)	Summary
Response helpers and startup polling tests/admin_auth_cors_ratelimit.rs	Adds response-returning GET, OPTIONS, and header helpers and updates /healthz polling to use them.
Status and header assertion migration tests/admin_auth_cors_ratelimit.rs	Updates authentication, signature, CORS, rate-limit, preflight, and health endpoint tests to assert directly on responses.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the test update for ureq 3 API drift.
Description check	✅ Passed	It covers the summary, fix details, and verification, and is mostly complete despite not following the template headings exactly.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/console-ureq3-test

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}