From: ebarendt@... Date: 2017-01-31T17:26:51+00:00 Subject: [ruby-core:79369] [Ruby trunk Bug#13171] URI::FTP path has a trailing slash when just hostname and scheme provided Issue #13171 has been updated by Eric Barendt. Robert A. Heiler wrote: > Should .to_s ever change the representation or given input to tokens that were not part of the original input? > Because the '/' was not part of it. > Anyway, I guess it is indeed the correct behaviour even if it seems weird. I disagree that it's correct. But it's also inconsistent with HTTP. Further, where does the "/" come from anyway? ~~~ ruby >> URI.parse("http://example.com").path => "" >> URI.parse("ftp://example.com").path => "" ~~~ ---------------------------------------- Bug #13171: URI::FTP path has a trailing slash when just hostname and scheme provided https://bugs.ruby-lang.org/issues/13171#change-62797 * 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: