Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gridftp: Use example message from RFC 2428 for response to EPSV #132

Merged
merged 1 commit into from
Aug 27, 2020

Conversation

fscheiner
Copy link
Member

Title says it all.

Not a big change, but from now on the Globus GridFTP server should use the exact example message for a response to EPSV from RFC 2428, although the difference to a response to PASV could be already seen from the differences in the actual data part of the response (e.g. (1,2,3,4,195,80) (in response to PASV) and (|||50000|) (in response to EPSV)).

The difference to RFC 2428 was noticed during testing UberFTP 2.9-Beta against a Globus GridFTP server 13.20. UberFTP 2.9-Beta uses EPSV and EPRT by default (both commands are compatible with IPv4 and IPv6 address families) instead of PASV and PORT .

@msalle, @ellert: Sorry, but I'm again unsure about what to change in addition (major, minor version of "globus-gridftp-server-control" and "globus-gridftp-server", packaging information, library version) as this is not a functionality change and I don't expect clients to behave differently due to the changed message. Could you please help me out? :-)

Copy link
Member

@msalle msalle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look fine to me, as for the version number change, I'm not entirely sure.

@fscheiner
Copy link
Member Author

@ellert: Thanks for making the needed changes to versions and packaging metadata.

@fscheiner fscheiner merged commit 85430f6 into gridcf:master Aug 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants