net/url - Go Issues

Go Issues Packages

net/url

Host/Port extraction malfunctions with IPv6 addressesNeedsInvestigation

#31024 opened 4 weeks ago by noneymous

1

Parse interprets octal literals in IP addresses as decimal onesNeedsInvestigation

#30999 opened 1 month ago by opennota

3

URL.String() does not escape QueryNeedsInvestigationhelp wanted

#30922 opened 1 month ago by vladimiroff

9

Parse does not permit percent escapes in hostNeedsFixSuggestedhelp wanted

#30844 opened 1 month ago by zombiezen

6

Parse documentation does not adequately explain escaping rules or RFC complianceDocumentationNeedsInvestigationWaitingForInfohelp wanted

#30611 opened 1 month ago by neilalexander

6

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

#30025 opened 2 months ago by nathj07

7

fails to decode %ya whereas browsers are more tolerantNeedsDecision

#29808 opened 3 months ago by Darkemon

2

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

#29662 opened 3 months ago by clausti

1

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

#29603 opened 3 months ago by Gregable

6

misleading error message when url has a leading spaceNeedsFix

#29261 opened 4 months ago by stefanb

14

URL.Parse Multiple Parsing IssuesNeedsInvestigation

#29098 opened 4 months ago by wir3less

18

PathEscape treatment of reserved characters is inconsistentNeedsInvestigation

#27559 opened 7 months ago by gibson042

4

';' is parsed as a separator in query stringGo2NeedsDecision

#25192 opened 11 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