Document location restrictions on Log4j 1 external entities - #4265
Merged
Merged
Conversation
ppkarwasz
force-pushed
the
fix/2.x/xml-entity-restrictions-docs
branch
from
August 30, 2026 09:54
c05fd82 to
5278cc6
Compare
ppkarwasz
force-pushed
the
fix/2.x/xml-entity-restrictions-docs
branch
2 times, most recently
from
August 30, 2026 15:16
4d7131e to
ceaeeb4
Compare
Yoyis8836
approved these changes
Aug 31, 2026
ramanathan1504
left a comment
ramanathan1504
left a comment
Contributor
There was a problem hiding this comment.
@ppkarwasz Changelog is missing
Member
Author
This is documentation only, so I wouldn't add any changelog. For me a changelog is necessary, so users can rapidly find a change that might have broken their application. In this case, no code changes are present. |
Contributor
ok understood👍 |
ppkarwasz
added
the
port-done
ppkarwasz
force-pushed
the
fix/2.x/xml-entity-restrictions-docs
branch
from
September 15, 2026 19:41
3e70cc9 to
f33fbeb
Compare
ramanathan1504
approved these changes
Sep 17, 2026
Since version 2.27.0 (#4198), the external subset and other external entities in Log4j 1 XML configuration files are resolved through `ConfigurationSource`, so they can only be retrieved from locations allowed by the `log4j2.configurationAllowedProtocols` property. Document this in the migration guide and in the Javadoc of the bridge `XmlConfiguration`. Assisted-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LNsw2hhNuJ6tjsEU2tChnn
Co-authored-by: Ramanathan <ramanathanbscmca@gmail.com>
ramanathan1504
force-pushed
the
fix/2.x/xml-entity-restrictions-docs
branch
from
September 17, 2026 07:11
a80b994 to
893d8d0
Compare
github-project-automation
Bot
moved this from Approved
to Merged
in Log4j pull request tracker
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #4264; only the last commit belongs to this PR.
Documents the behavior introduced by #4198, which first ships in
2.27.0: the external subset and other external entities in Log4j 1 XML configuration files are resolved throughConfigurationSource, so they can only be retrieved from locations allowed by thelog4j2.configurationAllowedProtocolsproperty. Adds a note to the migration guide and a paragraph to the Javadoc of the bridgeXmlConfiguration.Kept separate from #4264 so that the documentation of unreleased behavior can be merged (or held back) independently. After #4264 merges, the base can be retargeted to
2.x.🤖 Generated with Claude Code
https://claude.ai/code/session_01LNsw2hhNuJ6tjsEU2tChnn