I want to make a Servlet filter that will read the contents of the Response after it's been processed and completed and return that information in XML or PDF or whatever. But I'm not sure how to get any information out of the HttpServletResponse object. How can I get at this information?
Add a comment
|
4 Answers
Add this to the filter java file.
static class MyHttpServletResponseWrapper
extends HttpServletResponseWrapper {
private StringWriter sw = new StringWriter(BUFFER_SIZE);
public MyHttpServletResponseWrapper(HttpServletResponse response) {
super(response);
}
public PrintWriter getWriter() throws IOException {
return new PrintWriter(sw);
}
public ServletOutputStream getOutputStream() throws IOException {
throw new UnsupportedOperationException();
}
public String toString() {
return sw.toString();
}
}
Use the follow code:
HttpServletResponse httpResponse = (HttpServletResponse) response;
MyHttpServletResponseWrapper wrapper =
new MyHttpServletResponseWrapper(httpResponse);
chain.doFilter(request, wrapper);
String content = wrapper.toString();
The content variable now has the output stream. You can also do it for binary content.
4 Comments
DyreSchlock
Yeah, using an Servlet Reponse Wrapper and capturing output when it's written is about the best way to do it, I think.
DyreSchlock
The code that handles the request is using the output stream though. The TeeOutputStream can be used. ( commons.apache.org/io/apidocs/org/apache/commons/io/output/… )
asgs
what's a reasonable value of
BUFFER_SIZE?
user2602807
Have created LoggingFilter implements Filter, registered it, use your code and it does not work, just emtry strings on the exit. Could you show full (completed) version code?
Spring now has feature for it . All you need to do is use [ContentCachingResponseWrapper], which has method public byte[] getContentAsByteArray() .
I Suggest to make WrapperFactory which will allow to make it configurable, whether to use default ResponseWrapper or ContentCachingResponseWrapper.
1 Comment
Siva
See stackoverflow.com/questions/39935190/… for details.
I don't much know that you can get data out of an HttpServletResponse object as such. It may make more sense to structure your application such that requests are proxied to the appropriate handlers and passed about with data transfer objects, from which you can build the appropriate final response. In this manner, you never modifiy more than one response object or need to read from such.
Not a direct answer, I know, but that's how I'd do it give the question.
1 Comment
DyreSchlock
Ultimately, I'd do the same thing and put myself in a position where I wouldn't have to read for the response. But the actually request processing I'm using is fairly black boxed and can't be messed with :/
I don't believe you can necessarily do this given that writing to the output stream may result in the data being flushed to the client prior to any servlet filters being invoked post-population. As iftrue suggests, a different architecture would be advisable, to generate your XML (say) and then regenerate in whatever output format you desire.
EDIT: Having read your response to iftrue's posting, if you really can't interfere with the current processing, perhaps you require a servlet to proxy your request, capture the output from the original output, and then munge as appropriate. Very nasty, however :-(
