net/url - Go Issues

Go Issues Packages

net/url

parsing leaves a trailing `=` on the query params when there is only a single keyFeatureRequestNeedsDecision

#30025 opened 2 weeks ago by nathj07

7

fails to decode %ya whereas browsers are more tolerantNeedsDecision

#29808 opened 4 weeks ago by Darkemon

2

clarify in docs that RawPath is not always set by Parse()Documentation

#29662 opened 1 month ago by clausti

0

add URL.ForceFragment like ForceQuery for empty fragments to stringify with '#'NeedsDecision

#29603 opened 1 month ago by Gregable

6

misleading error message when url has a leading spaceNeedsFix

#29261 opened 2 months ago by stefanb

13

URL.Parse Multiple Parsing IssuesNeedsInvestigation

#29098 opened 2 months ago by wir3less

18

PathEscape treatment of reserved characters is inconsistentNeedsInvestigation

#27559 opened 5 months ago by gibson042

4

';' is parsed as a separator in query stringGo2NeedsDecision

#25192 opened 9 months ago by zhyale

6

URL allows malformed query round tripNeedsDecision

#22907 opened 1 year ago by artyom

21

username in authority is not strictly in RFC3986NeedsInvestigation

#22655 opened 1 year ago by mattn

2

optimize unescape and escapePerformancehelp wanted

#17860 opened 2 years ago by dsnet

10