生产中的ServletRequestWrapper或ServletResponseWrapper？ [英] ServletRequestWrapper or ServletResponseWrapper in production?

问题描述

您好，你看到任何非常有用的扩展 HttpServletResponseWrapper / HttpServletRequestWrapper 或 ServletRequestWrapper / ServletResponseWrapper ？

Hi have you seen anything really useful extending HttpServletResponseWrapper/HttpServletRequestWrapper or ServletRequestWrapper/ ServletResponseWrapper in production environment?

推荐答案

• 从生成的HTML中修剪空白，可以节省超过50％的带宽。我有一个显示大表格数据的项目（带有很好的缩进HTML源代码），只需修剪所有空格，响应大小从大约200KB到大约70KB。


• 处理多部分/表格-data通过将多部分表单数据放回请求参数映射中来透明地请求，以便您可以使用 request.getParameter（）并再次采用常规方式（ Servlet< = 2.5示例， Servlet> = 3.0示例）。


• 捕获输出流要么复制，要么 MD5-hash 它。


• 禁用URL重写 。


• Trim whitespace from generated HTML, can save over 50% of bandwidth. I've had a project which displays large tabular data (with nicely indented HTML source), response size went from ~200KB to ~70KB by just trimming all whitespace away.
• Process multipart/form-data requests transparently by putting multipart form data back in request parameter map so that you can use request.getParameter() and consorts the usual way again (Servlet <=2.5 example, Servlet >=3.0 example).
• Capture the outputstream, either to have a copy or to MD5-hash it.
• Disabling URL rewriting.

Etcetera .. Etcetera ..所有只是为了覆盖和更改某些 HttpServletRequest的默认行为 / HttpServletResponse 方法。

Etcetera.. Etcetera.. All just to override and change the default behaviour of certain HttpServletRequest/HttpServletResponse methods.

这篇关于生产中的ServletRequestWrapper或ServletResponseWrapper？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！