Built-in {UpstreamScheme} placeholder - #2201
rocleegithub wants to merge 2 commits into
Conversation
|
@rocleegithub Please, resolve merge conflicts! |
{UpstreamScheme} placeholder
c216cdf to
b458f0f
Compare
4ef4275 to
3e92ddd
Compare
908d84f to
0678e7a
Compare
|
Do you want me to take care of the merge conflicts in your pull request? |
|
@raman-m Any progress on this? |
|
You can see the progress yourself. The author has not been responsive since November 2024. I have done some work on this PR in his absence, particularly resolving all merge conflicts during 2025 for several major releases, to keep it updated and ready for potential code reviews. Please ask the author, a Chinese developer, whether he still intends to make a proper contribution to the product, rather than leaving this pull request as a draft. P.S. The approximate time when I may return to this PR is after the release of .NET 10, not earlier. The milestone must be closed. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #2201 +/- ##
========================================
Coverage 95.55% 95.55%
========================================
Files 264 264
Lines 6970 6978 +8
Branches 761 761
========================================
+ Hits 6660 6668 +8
Misses 201 201
Partials 109 109
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
c2fb365 to
a5efd3c
Compare
11ba99c to
78c983d
Compare
aff38ad to
e9225f3
Compare
New Feature #2193 #2195
Discussion thread
Support like this Placeholders for X-Forwarded-Proto #2195
"X-Forwarded-Proto": "{UpstreamScheme}"