exceptionfactory opened a new pull request, #6030: URL: https://github.com/apache/nifi/pull/6030
# Summary [NIFI-9990](https://issues.apache.org/jira/browse/NIFI-9990) Improves handling of FTP `550` reply codes to detect whether the reply message indicates that the file is not found or that there is a permission restriction. The `550` reply code indicates that the remote file is unavailable, but does not indicate the specific reason. The current file not found detection is based on a specific message, and does not indicate permission problems. Changes include using a more flexible regular expression pattern to detect when a file is not found. If the reply message does not match the pattern, the `550` reply code results in a permission denied exception. Additional updates include adding unit tests to exercise these conditions. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [x] JDK 8 - [ ] JDK 11 - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
