From: matthew@... Date: 2017-01-31T11:46:46+00:00 Subject: [ruby-core:79364] [Ruby trunk Bug#13171] URI::FTP path has a trailing slash when just hostname and scheme provided Issue #13171 has been updated by Matthew Kerwin. If you take the URI object as a data structure with components then any stringification that round-trips through parsing is fine. This is true of any normalisation or canonicalisation. It's only an issue if you think of the URI as a string. ---------------------------------------- Bug #13171: URI::FTP path has a trailing slash when just hostname and scheme provided https://bugs.ruby-lang.org/issues/13171#change-62792 * Author: Milo Price * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- As with HTTP uris, the trailing slash on a FTP uri should be optional, per RFC 1738 (ftp://ftp.funet.fi/pub/doc/rfc/rfc1738.txt). However, under the current implementation, URI::FTP#to_s always has a trailing slash when only a hostname is provided (i.e., no path): ~~~ ruby URI.parse("http://example.com").to_s => "http://example.com" URI.parse("ftp://example.com").to_s => "ftp://example.com/" ~~~ -- https://bugs.ruby-lang.org/ Unsubscribe: