takraj opened a new pull request, #10919: URL: https://github.com/apache/nifi/pull/10919
If a client sends the request with `Transfer-Encoding: chunked`, then this header was not removed when NiFi forwarded it to the rest of the cluster, but it added `Content-Length: ####` and encoded the actual replicated request according to `Content-Length` rule. The receiving NiFi instance therefore had to deal with a request with both headers present, and it rejected it. Even if it would accept such requests, it should have been interpreted according to `Transfer-Encoding` rule, and would have failed to find the chunk boundaries in that case, and would have failed to parse it. Ref: https://www.rfc-editor.org/rfc/rfc9112 **Important quotes:** 6.1. Transfer-Encoding > Early implementations of `Transfer-Encoding` would occasionally send > both a chunked transfer coding for message framing and an estimated > `Content-Length` header field for use by progress bars. This is why > `Transfer-Encoding` is defined as overriding `Content-Length`, as > opposed to them being mutually incompatible. > ... > A server MAY reject a request that contains both `Content-Length` > and `Transfer-Encoding` or process such a request in accordance > with the `Transfer-Encoding` alone. 6.2. Content-Length > A sender MUST NOT send a `Content-Length` header field in any message > that contains a `Transfer-Encoding` header field. <!-- 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-15625](https://issues.apache.org/jira/browse/NIFI-15625) # 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 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]
