org.mockftpserver.fake.command.RntoCommandHandler Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of MockFtpServer Show documentation

The MockFtpServer project provides mock/dummy FTP server implementations for testing FTP client code. Two FTP Server implementations are provided, each at a different level of abstraction. FakeFtpServer provides a higher-level abstraction. You define a virtual file system, including directories and files, as well as a set of valid user accounts and credentials. The FakeFtpServer then responds with appropriate replies and reply codes based on that configuration. StubFtpServer, on the other hand, is a lower-level "stub" implementation. You configure the individual FTP server commands to return custom data or reply codes, allowing simulation of either success or failure scenarios. You can also verify expected command invocations.

There is a newer version: 3.2.0

Show newest version

/*
 * Copyright 2008 the original author or authors.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.mockftpserver.fake.command;

import org.mockftpserver.core.command.Command;
import org.mockftpserver.core.command.ReplyCodes;
import org.mockftpserver.core.session.Session;
import org.mockftpserver.core.session.SessionKeys;

/**
 * CommandHandler for the RNTO command. Handler logic:
 * 
 * If the user has not logged in, then reply with 530
 * If this command was not preceded by a valid RNFR command, then reply with 503
 * If the required TO pathname parameter is missing, then reply with 501
 * If the TO pathname parameter does not specify a valid filename, then reply with 553
 * If the TO pathname parameter specifies an existing directory, then reply with 553
 * If the current user does not have write access to the parent directory, then reply with 553
 * Otherwise, rename the file, remove the FROM path stored in the session by the RNFR command, and reply with 250
 * 
 * The supplied pathname may be absolute or relative to the current directory.
 *
 * @author Chris Mair
 */
public class RntoCommandHandler extends AbstractFakeCommandHandler {

    protected void handle(Command command, Session session) {
        verifyLoggedIn(session);
        String toPath = getRealPath(session, command.getRequiredParameter(0));
        String fromPath = (String) getRequiredSessionAttribute(session, SessionKeys.RENAME_FROM);

        this.replyCodeForFileSystemException = ReplyCodes.WRITE_FILE_ERROR;
        verifyFileSystemCondition(!getFileSystem().isDirectory(toPath), toPath, "filesystem.isDirectory");

        // User must have write permission to the directory
        String parentPath = getFileSystem().getParent(toPath);
        verifyFileSystemCondition(notNullOrEmpty(parentPath), parentPath, "filesystem.doesNotExist");
        verifyFileSystemCondition(getFileSystem().exists(parentPath), parentPath, "filesystem.doesNotExist");
        verifyWritePermission(session, parentPath);

        getFileSystem().rename(fromPath, toPath);

        session.removeAttribute(SessionKeys.RENAME_FROM);
        sendReply(session, ReplyCodes.RNTO_OK, "rnto", list(fromPath, toPath));
    }

}