Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.04%. Comparing base (1133ceb) to head (dd808d6).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master   #13821   +/-   ##
=======================================
  Coverage   99.03%   99.04%           
=======================================
  Files         135      135           
  Lines       51282    51378   +96     
  Branches     2691     2693    +2     
=======================================
+ Hits        50787    50885   +98     
+ Misses        372      371    -1     
+ Partials      123      122    -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

Confidence Score: 5/5

[Critical risk] Changes how the web server validates and interprets request URLs.

No outstanding findings block merging.

_{Reviews (5) · Last reviewed commit: "Apply suggestion from @Dreamsorcerer"}

Merging this PR will not alter performance

✅ 97 untouched benchmarks
⏩ 83 skipped benchmarks¹

_{Comparing absolute-scheme (dd808d6) with master (040c65e)}

Backport to 3.15: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply a921cfd on top of patchback/backports/3.15/a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df/pr-13821

Backporting merged PR #13821 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   git remote add upstream https://github.com/aio-libs/aiohttp.git
   

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   git fetch upstream
   git checkout -b patchback/backports/3.15/a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df/pr-13821 upstream/3.15
   

4. Now, cherry-pick PR Use protocol scheme for absolute-form requests #13821 contents into that branch:

   git cherry-pick -x a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df
   

   If it'll yell at you with something like fatal: Commit a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df is a merge but no -m option was given., add -m 1 as follows instead:

   git cherry-pick -m1 -x a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df
   

5. At this point, you'll encounter some merge conflicts. You must
   resolve them in order to preserve the patch from PR Use protocol scheme for absolute-form requests #13821 as close to the
   original as possible.
6. Once conflicts are resolved and git added, run:

   git cherry-pick --continue
   

7. Push this branch to your fork on GitHub:

   git push origin patchback/backports/3.15/a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df/pr-13821
   

8. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Backport to 3.14: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply a921cfd on top of patchback/backports/3.14/a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df/pr-13821

Backporting merged PR #13821 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   git remote add upstream https://github.com/aio-libs/aiohttp.git
   

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   git fetch upstream
   git checkout -b patchback/backports/3.14/a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df/pr-13821 upstream/3.14
   

4. Now, cherry-pick PR Use protocol scheme for absolute-form requests #13821 contents into that branch:

   git cherry-pick -x a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df
   

   If it'll yell at you with something like fatal: Commit a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df is a merge but no -m option was given., add -m 1 as follows instead:

   git cherry-pick -m1 -x a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df
   

5. At this point, you'll encounter some merge conflicts. You must
   resolve them in order to preserve the patch from PR Use protocol scheme for absolute-form requests #13821 as close to the
   original as possible.
6. Once conflicts are resolved and git added, run:

   git cherry-pick --continue
   

7. Push this branch to your fork on GitHub:

   git push origin patchback/backports/3.14/a921cfd0fec28d5a9e5bf8d6f4372b8fa63c49df/pr-13821
   

8. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.