kevdoran opened a new pull request, #11094: URL: https://github.com/apache/nifi/pull/11094
<!-- Licensed to the Apache Software Foundation (ASF) under one or more --> <!-- contributor license agreements. See the NOTICE file distributed with --> <!-- this work for additional information regarding copyright ownership. --> <!-- The ASF licenses this file to You 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. --> # Summary [NIFI-15784](https://issues.apache.org/jira/browse/NIFI-15784) UploadRequest replication (used for asset and NAR uploads) did not forward inbound servlet headers to peer nodes. Only three explicit headers (filename, content-type, cluster-id-generation-seed) were included. This caused ConnectorRequestContext to not have the full original request context. Standard cluster replication (ThreadPoolRequestReplicator) already forwards all inbound headers via ApplicationResource.getHeaders(), with appropriate stripping of credentials, hop-by-hop headers, and replication protocol headers. Upload replication now use the same approach for consistency. - Extract shared header-preparation logic into ReplicationHeaderUtils so credential stripping, proxied-entity injection, and replication header sanitisation cannot drift between the two replication paths - Add UploadRequest.forwardRequestHeaders(Map) so callers can opt in to forwarding inbound servlet headers - Rebuild outbound headers in StandardUploadRequestReplicator using a secure pipeline: strip replication headers, strip hop-by-hop, apply explicit builder headers, apply proxy/credential policy, force-set replication flags - Wire all current upload call sites (ConnectorResource.createAsset, ParameterContextResource asset upload, ControllerResource.uploadNar) to forward inbound headers - Use File.length() instead of InputStream.available() for reliable content-length in upload replication # 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` - [x] Pull request contains [commits signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with a registered key indicating `Verified` status ### 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 `./mvnw clean install -P contrib-check` - [x] JDK 21 - [ ] JDK 25 ### Licensing - [x] 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) - [x] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [x] 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]
