oscerd opened a new pull request, #23561:
URL: https://github.com/apache/camel/pull/23561
Backports #23437 to \`camel-4.14.x\`.
Cherry-pick of merge commit \`bdcfe4960\` with two adaptations:
1. The original PR's upgrade-guide entry was added to
\`camel-4x-upgrade-guide-4_21.adoc\`, which does not exist on 4.14.x. Per
the project's backport policy the same content has been added to
\`camel-4x-upgrade-guide-4_14.adoc\` in the \`== Upgrading from 4.14.7 to
4.14.8\` section instead.
2. The original commit also converted three \`@Metadata\` descriptions from
string concatenation to text blocks. On 4.14.x the existing string-concat
formatting has been **preserved**; only the four header string values are
changed.
## Summary
Renames the four Exchange header string values in \`PdfHeaderConstants\` to
\`CamelPdf<Name>\` so they fall under the default \`HeaderFilterStrategy\`:
| Constant | Previous value | New value |
|----------|----------------|-----------|
| \`PdfHeaderConstants.PROTECTION_POLICY_HEADER_NAME\` |
\`protection-policy\` | \`CamelPdfProtectionPolicy\` |
| \`PdfHeaderConstants.PDF_DOCUMENT_HEADER_NAME\` | \`pdf-document\` |
\`CamelPdfDocument\` |
| \`PdfHeaderConstants.DECRYPTION_MATERIAL_HEADER_NAME\` |
\`decryption-material\` | \`CamelPdfDecryptionMaterial\` |
| \`PdfHeaderConstants.FILES_TO_MERGE_HEADER_NAME\` | \`files-to-merge\` |
\`CamelPdfFilesToMerge\` |
These headers carry security-sensitive PDFBox objects (\`PDDocument\`,
\`DecryptionMaterial\`, \`ProtectionPolicy\`); aligning with the \`Camel\`
namespace lets the default header filter strip them at transport boundaries.
## Test plan
- [x] \`mvn test\` in \`components/camel-pdf\` on 4.14.x — passes
- [x] String-concat formatting of pre-existing \`@Metadata\` descriptions
preserved (avoids touching unrelated code on the maintenance branch)
- [x] Upgrade-guide entry added in \`camel-4x-upgrade-guide-4_14.adoc\`
Tracker: CAMEL-23577
_Reported by Claude Code on behalf of Andrea Cosentino_
--
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]
