fix: X-Forwarded-Proto rejected when allowedDomains includes protocol field
#15560Comparing
z0mt3c:fix/forwarded-proto-allowed-domains
(31af714
) withmain
(7be3308
)+33%
- Improvement
- 2
- Untouched
- 7
No successful run was found on main ( 55c568c) during the generation of this report, so 7be3308 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.
Benchmarks
9 total
Rendering: streaming [false], .md file
benchmark/bench/render.bench.js::Bench rendering+33%
1.5 ms1.1 ms
Build: hybrid site (static + server)
benchmark/bench/build-hybrid.bench.js::Bench build time+11%
8.5 s7.7 s
Rendering: streaming [false], .astro file
benchmark/bench/render.bench.js::Bench rendering+2%
337.1 ms330.4 ms
Build: full server site
benchmark/bench/build-server.bench.js::Bench build time0%
8.3 s8.3 s
Rendering: streaming [false], .mdx file
benchmark/bench/render.bench.js::Bench rendering0%
587 ms586.7 ms
Rendering: streaming [true], .md file
benchmark/bench/render.bench.js::Bench rendering0%
1.1 ms1.1 ms
Rendering: streaming [true], .mdx file
benchmark/bench/render.bench.js::Bench rendering0%
586.6 ms588.1 ms
Build: full static site
benchmark/bench/build-static.bench.js::Bench build time-1%
3.5 s3.6 s
Rendering: streaming [true], .astro file
benchmark/bench/render.bench.js::Bench rendering-3%
338 ms347.9 ms
Commits
Click on a commit to change the comparison rangeBase
main
7be3308
+32.87%
fix: X-Forwarded-Proto rejected when allowedDomains includes protocol and hostname
31af714
4 hours ago
by z0mt3c