fix browser warnings related to crossorigin preload

[silverwind]

I don't fully understand why Chrome would consider these requests cross-origin when they are clearly same-origin in my view. Anyways, this should get rid of the console warning. I did try with-credentials but that seemed to have no effect.

Fixes: #9976 (comment) @zeripath

[codecov-io]

Codecov Report

Merging #9984 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9984      +/-   ##
==========================================
- Coverage   42.26%   42.25%   -0.02%     
==========================================
  Files         610      610              
  Lines       80370    80370              
==========================================
- Hits        33971    33960      -11     
- Misses      42221    42230       +9     
- Partials     4178     4180       +2

Impacted Files	Coverage Δ
services/pull/update.go	51.16% <0%> (-3.49%)	⬇️
services/pull/patch.go	64.77% <0%> (-3.15%)	⬇️
models/unit.go	37.03% <0%> (-2.47%)	⬇️
routers/repo/view.go	38.59% <0%> (-0.88%)	⬇️
modules/queue/workerpool.go	42.48% <0%> (+1.28%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a83c373...1f77f6b. Read the comment docs.

[guillep2k]

I don't fully understand why Chrome would consider these requests cross-origin when they are clearly same-origin in my view.

Maybe there's a redirection in play?

[silverwind]

No, those are direct responses. I think it's just a useless detail in that preload spec.