Upstream contribution · go-resty/resty
resty · Normalizing Resty load-balancer URLs before joining request paths
Problem
A base URL with a fragment or a bare question-mark could absorb the request path when combined with the caller's relative URL. In the fragment example, a caller requesting /requested reached the upstream server's root.
Engineering response
The client clears fragment-related fields and the empty-query marker alongside its existing base-path and query normalization.
Evidence and scope
The regression uses a loopback HTTP server through Resty's public load-balancer API. The PR reports three baseline failures and a passing ordinary-query control, followed by four passing cases and a passing full Go suite on the candidate.