From: hhelibebcnofnenamg@gmail•com
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:50086] [Ruby trunk Feature#13382] [PATCH] Options for FTP PORT command
Date: Tue, 18 Apr 2017 08:58:56 +0000 [thread overview]
Message-ID: <redmine.journal-64349.20170418085855.f56bde5d7b29e71a@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13382.20170329083629@ruby-lang.org
Issue #13382 has been updated by osa (Shunsuke OSA).
shugo (Shugo Maeda) wrote:
> The name data_listening_address= seems misleading because it doesn't
> change the address to be bound.
I see. It is reasonable.
> And data_listening_port= is less flexible than setActivePortRange()
> because it doesn't allow multiple port numbers.
This is reasonable too.
But as you know, PORT command can send only one port number.
I will implement that Net::FTP choose one of the port number in the range randomly.
(FTPClient of Apache Commons does so)
----------------------------------------
Feature #13382: [PATCH] Options for FTP PORT command
https://bugs.ruby-lang.org/issues/13382#change-64349
* Author: osa (Shunsuke OSA)
* Status: Open
* Priority: Normal
* Assignee: shugo (Shugo Maeda)
* Target version:
----------------------------------------
# Abstract
Add options to Net::FTP to set data listening host and port.
# Background
Net::FTP sends local address and default port to remote FTP server.
In FTP active mode, remote server will connect to client to establish data connection, but it will fail if there is NAT in network.
(NAT doesn't rewrite address and port in PORT command because they are not in packet header but payload)
So, it's necessary to set host and port for FTP PORT command explicitly.
# Real use cases
Active FTP is not working in AWS EC2.
- https://forums.aws.amazon.com/thread.jspa?messageID=75667 (Login required)
- http://osa.hatenablog.com/entry/2015/02/24/134826 (Japanese)
# Pull request
- https://github.com/ruby/ruby/pull/1561
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2017-04-18 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-13382.20170329083629@ruby-lang.org>
2017-03-29 8:36 ` [ruby-dev:50057] [Ruby trunk Feature#13382] [PATCH] Options for FTP PORT command hhelibebcnofnenamg
2017-03-29 9:24 ` [ruby-dev:50058] " shugo
2017-03-29 14:44 ` [ruby-dev:50060] " hhelibebcnofnenamg
2017-03-30 4:47 ` [ruby-dev:50061] " shugo
2017-03-30 5:10 ` [ruby-dev:50062] " shugo
2017-04-15 7:21 ` [ruby-dev:50079] " hhelibebcnofnenamg
2017-04-17 5:09 ` [ruby-dev:50083] " shugo
2017-04-18 8:58 ` hhelibebcnofnenamg [this message]
2017-12-04 6:40 ` [ruby-dev:50334] " hhelibebcnofnenamg
2017-12-04 8:15 ` [ruby-dev:50335] [Ruby trunk Feature#13382][Rejected] " shugo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-64349.20170418085855.f56bde5d7b29e71a@ruby-lang.org \
--to=ruby-dev@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).