[
https://issues.apache.org/jira/browse/CXF-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080888#comment-18080888
]
Fabio Burzigotti commented on CXF-9212:
---------------------------------------
Thanks for creating this issue [~reta].
BTW, this affects Apache CXF 4.1.x (specifically 4.1.6 which was released
yesterday) too, not just 4.2.0.
Could you please fix the Jira fields accordingly?
The JBoss WS CXF {{main}} branch is currently consuming 4.1.5, where the issue
is not present, but we should cut out a 7.4.0.Final release soon.
Such version would then be included in WildFly, to ultimately start consuming
the Apache CXF 4.1.x stream artifacts.
As stated in the CXF Dev list [1], this would result in a regression for
WildFly users, where the "vfs" schema is used for deployment resources.
[1]
https://lists.apache.org/thread/2nydyzsofmz0kgl9k6n9gyp1088sm2f5
> Restrict valid URL protocols in TLSParameterJaxBUtils and URIResolver
> ---------------------------------------------------------------------
>
> Key: CXF-9212
> URL: https://issues.apache.org/jira/browse/CXF-9212
> Project: CXF
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: Andriy Redko
> Assignee: Colm O hEigeartaigh
> Priority: Major
> Fix For: 4.2.1
>
>
> Restrict valid URL protocols in TLSParameterJaxBUtils and URIResolver to
> sensible defaults: "file", "http", "https", "jar", "zip", "wsjar", "local",
> "classpath"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
