Apache Shiro and REST DSL routes
Is there any documentation or examples that I can look at to understand how I can secure my Camel REST routes? Ideally I'd like to leverage Keycloak and Shiro for my AuthN/AuthZ. Let me know if there is anything out there I can leverage. Thanks
Re: Empty stream for gzipped response
Sure. The Server is jetty from camel-jetty. Message body is: org.apache.camel.converter.stream.InputStreamCache for exchange.getIn().getBody() (empty) org.apache.camel.converter.stream.ByteArrayInputStreamCache for message.getBody() (not empty) вт, 17 янв. 2023 г. в 16:59, Claus Ibsen : > > Hi > > Thanks for reporting. Can you tell a bit more about what HTTP server you > are using? And what class type the message body is at that moment in > doWriteGZIPResponse? > If the body is not an instance of InputStream then what type is that body > of yours? > > > On Tue, Jan 17, 2023 at 1:03 PM Dmitri T wrote: > > > Hello. > > After upgrading from Camel 3.7.x to the recent version, gzipped > > response (Content-Encoding: gzip) from a route comes empty. I have > > found an issue CAMEL-13092 (fixed in Camel 3.10) which caused that in > > > > camel-http-common/src/main/java/org/apache/camel/http/common/DefaultHttpBinding.java > > (line 602 doWriteGZIPResponse method): Object body = > > exchange.getIn().getBody(); > > I debugged and found. that stream was not empty, if that line was > > replaced by Object body = message.getBody(InputStream.class);, like it > > was done for plain non-gzipped response in doWriteDirectResponse > > method. > > I have tested this change with ServletStreamingGzipChunkedTest > > successfully. > > Is this an issue and could be fixed in the next Camel release? > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Best regards, Dmitri
Re: Empty stream for gzipped response
Hi Thanks for reporting. Can you tell a bit more about what HTTP server you are using? And what class type the message body is at that moment in doWriteGZIPResponse? If the body is not an instance of InputStream then what type is that body of yours? On Tue, Jan 17, 2023 at 1:03 PM Dmitri T wrote: > Hello. > After upgrading from Camel 3.7.x to the recent version, gzipped > response (Content-Encoding: gzip) from a route comes empty. I have > found an issue CAMEL-13092 (fixed in Camel 3.10) which caused that in > > camel-http-common/src/main/java/org/apache/camel/http/common/DefaultHttpBinding.java > (line 602 doWriteGZIPResponse method): Object body = > exchange.getIn().getBody(); > I debugged and found. that stream was not empty, if that line was > replaced by Object body = message.getBody(InputStream.class);, like it > was done for plain non-gzipped response in doWriteDirectResponse > method. > I have tested this change with ServletStreamingGzipChunkedTest > successfully. > Is this an issue and could be fixed in the next Camel release? > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Empty stream for gzipped response
Hello. After upgrading from Camel 3.7.x to the recent version, gzipped response (Content-Encoding: gzip) from a route comes empty. I have found an issue CAMEL-13092 (fixed in Camel 3.10) which caused that in camel-http-common/src/main/java/org/apache/camel/http/common/DefaultHttpBinding.java (line 602 doWriteGZIPResponse method): Object body = exchange.getIn().getBody(); I debugged and found. that stream was not empty, if that line was replaced by Object body = message.getBody(InputStream.class);, like it was done for plain non-gzipped response in doWriteDirectResponse method. I have tested this change with ServletStreamingGzipChunkedTest successfully. Is this an issue and could be fixed in the next Camel release?
