Skip to content

Look into correct PASV behaviour #439

@robklg

Description

@robklg

There are some behaviours around PASV that need looking into:

  • We accept multiple pasv commands (and open new passive ports each time) - do we want to close the previous listening port, or not accept the new command?
  • With the timeout on pasv that was added: when the passive listening timeout is reached, how are we supposed to behave according to the RFC? Should we return some 4xx in response to the command that was received too late? (LIST, STOR, RETR)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions