[jira] [Created] (CXF-8829) How to add custom security output headers to apache karaf cxf listing page http://localhost:8181/cxf in apache-karaf 4.3.6
Jithu Thomas created CXF-8829: - Summary: How to add custom security output headers to apache karaf cxf listing page http://localhost:8181/cxf in apache-karaf 4.3.6 Key: CXF-8829 URL: https://issues.apache.org/jira/browse/CXF-8829 Project: CXF Issue Type: Wish Components: Configuration, JAX-RS Environment: I use apache-karaf 4.3.6 and java version "1.8.0_202" . Reporter: Jithu Thomas I want to understand how to add custom security output headers to apache karaf cxf listing page http://localhost:8181/cxf . As of now I can see the the output headers coming is content-type and content-length. I want to add the security headers also in output header after the http://localhost:8181/cxf request. I use apache-karaf 4.3.6 and java version "1.8.0_202" . I want to add the following headers to the output headers. Strict-Transport-Security X-Frame-Options X-XSS-Protection X-Content-Type-Options Content-Security-Policy What is the best way to achieve this. I tried adding properties to org.ops4j.pax.web.cfg file, but it didnt work out. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8826) AsyncHTTPConduit (hc5) - Unexpected EOF during response processing
[
https://issues.apache.org/jira/browse/CXF-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko reassigned CXF-8826:
-
Assignee: Andriy Redko
> AsyncHTTPConduit (hc5) - Unexpected EOF during response processing
> --
>
> Key: CXF-8826
> URL: https://issues.apache.org/jira/browse/CXF-8826
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 3.5.5
>Reporter: Magnus Holm
>Assignee: Andriy Redko
>Priority: Major
> Attachments: http-hc-wireshark.png, http-hc5-wireshark.png
>
>
> I'm encountering issues with large SOAP response payloads using the http-hc5
> {{AsyncHTTPConduit}}. It seems the stream-reader encounters an unexpected EOF
> while processing the stream. The issue is not reproducible with the http-hc
> {{AsyncHTTPConduit}}. Test-cases are linked below.
> I've also monitored the existing {{AsyncHTTPConduitTest}} with wireshark in
> both modules http-hc and http-hc5. While http-hc behaves as you'd expect,
> http-hc5 produces RST,ACK (reset) instead of the expected FIN,ACK, even when
> processing is seemingly successful. Attached a couple of screenshots to
> illustrate.
> Unfortunately I've not been able to pinpoint what the cause of the issue is.
> This has happened using three different backends, jetty, undertow and some
> ancient SOAP production system that I'm sure are running neither of those, so
> it seems the issue is at least on the client-side.
> Testcases: https://github.com/magnho/cxf/pull/1
> Fails with http-hc5, succeeds with http-hc.
> See:
> {{org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitLargeResponseTest}}
> {{org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitLargeResponseTest}}
> Please let me know if you need me to provide any further details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8815) Fix org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitTest.testResponseSameBufferSize
[ https://issues.apache.org/jira/browse/CXF-8815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8815: -- Fix Version/s: 3.6.0 4.0.1 3.5.6 3.4.11 > Fix > org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitTest.testResponseSameBufferSize > - > > Key: CXF-8815 > URL: https://issues.apache.org/jira/browse/CXF-8815 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.0, 4.0.1, 3.5.6, 3.4.11 > > > h1. Regression > org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitTest.testResponseSameBufferSize > Failing for the past 1 build (Since > [#335|https://ci-builds.apache.org/job/CXF/job/pipeline/job/main/335/] ) > [Took 70 > ms.|https://ci-builds.apache.org/job/CXF/job/pipeline/job/main/335/testReport/junit/org.apache.cxf.transport.http.asyncclient.hc5/AsyncHTTPConduitTest/testResponseSameBufferSize/history] > > h3. Stacktrace > java.lang.AssertionError at org.junit.Assert.fail(Assert.java:87) at > org.junit.Assert.fail(Assert.java:96) at > org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitTest.testResponseSameBufferSize(AsyncHTTPConduitTest.java:143) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:568) at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:377) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:284) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:248) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:167) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456) > at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169) > at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
