org.mockftpserver.fake.command.AppeCommandHandler 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;

/**
 * CommandHandler for the APPE command. Handler logic:
 * 
 * If the user has not logged in, then reply with 530 and terminate
 * If the required pathname parameter is missing, then reply with 501 and terminate
 * If the pathname parameter does not specify a valid filename, then reply with 553 and terminate
 * If the current user does not have write access to the named file, if it already exists, or else to its
 * parent directory, then reply with 553 and terminate
 * If the current user does not have execute access to the parent directory, then reply with 553 and terminate
 * Send an initial reply of 150
 * Read all available bytes from the data connection and append to the named file in the server file system
 * If file write/store fails, then reply with 553 and terminate
 * Send a final reply with 226
 * 
 *
 * @author Chris Mair
 */
public class AppeCommandHandler extends AbstractStoreFileCommandHandler {

    /**
     * @return the message key for the reply message sent with the final (226) reply
     */
    protected String getMessageKey() {
        return "appe";
    }

    /**
     * @return true if this command should append the transferred contents to the output file; false means
     *         overwrite an existing file.
     */
    protected boolean appendToOutputFile() {
        return true;
    }

}