HTTP module default changes in k6 v0.50 impacting script compatibility

The transition from k6 v0.47 to v0.50 introduced significant shifts in how the HTTP module handles implicit behaviors. Specifically, changes to default timeouts, redirect handling, and connection reuse logic create a compatibility boundary for scripts that relied on previous version-level defaults.

When upgrading without explicitly defining these options in the script, tests may exhibit altered latency profiles, unexpected error rates, or different retry outcomes. This is particularly problematic when maintaining baseline consistency across CI/CD pipelines where the underlying engine’s behavior might silently affect threshold‑based pass/fail decisions.

What specific HTTP options must be explicitly declared to replicate v0.47 behavior in v0.50, and how do the new connection reuse defaults affect metric accuracy in high‑concurrency scenarios compared to the previous versioning?