Repository navigation
fix: enable HTTP/2 for CLI RDAP requests - #57
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Warning Review limit reachedNext included review available in 37 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
Merge Risk: ⚪ Minimal · up to The HTTP/2 change has no identified issue that needs resolution before merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
3e2be59 to
dbb8035
Compare
Inherits HTTP/2, proxy, and timeout defaults instead of rebuilding them by hand.
|
Great stuff, thanks @RyougikiMikiya! I slightly refactored the transport to instead clone the default Go transport, as this also bakes in default timeouts and such which we should also be using. |
Summary
Fix RDAP CLI queries against servers that require HTTP/2, such as TWNIC.
Problem
The CLI creates a custom
http.Transportwith a custom TLS configuration. In this case, Go does not automatically attempt HTTP/2.TWNIC rejects HTTP/1.1 requests with
426 Upgrade Required, causing queries such as:to fail with:
Error: No RDAP servers responded successfully
Changes
Verification
https://ccrdap.twnic.tw/tw/domain/cheers.com.tw
The query now returns HTTP 200 and is decoded successfully.
Summary by CodeRabbit