转：Enabling HTTP request response logging on JBoss 4.2

最新推荐文章于 2024-11-15 18:38:47 发布

liu_g927

最新推荐文章于 2024-11-15 18:38:47 发布

阅读量132

点赞数

分类专栏： JBOSS 文章标签： java 运维

本文链接：https://blog.csdn.net/liu_g927/article/details/84211899

版权

JBOSS 专栏收录该内容

1 篇文章 0 订阅

订阅专栏

Enabling HTTP request response logging on JBoss 4.2

转自：http://blog.leenarts.net/2010/08/26/http-request-response-logging-jboss-4-2/

Today I had a bit of a fiddle with JBoss 4.2 due to IE7/IE8 compatibility differences.

When opening or downloading a file in IE7 over an SSL connection (HTTPS), IE7 requires a bit of HTTP header-fu to allow you to actually perform that action.

It’s simple really. Just add “Pragma: public” and “Cache-Control: maxage=3600″ to your HTTP headers and you’re good to go.

In Java code:

 
         response.setHeader( 
         "Pragma" 
         ,  
         "public" 
         ); 
        
         response.setHeader( 
         "Cache-Control" 
         ,  
         "maxage=3600" 
         );

To check if it’s working was a different matter. How to check the HTTP header content when things get sent over an HTTPS connection… FireBug doesn’t work, and so doesn’t any other developer tooling in any browser. Tracing the network traffic is pretty useless too, it’s encrypted. Last option, trace it on the server. Simply enabling network tracing on the Java VM didn’t work. For some reason JBoss doesn’t pick up this Java VM setting, probably because they are using a NIO based stack or something. I really don’t know.

JBoss does use Catalina for it’s HTTP/HTTPS/Web container handling. Catalina is another name for Tomcat. Tomcat has this valve thing which allows you to plug into the processing pipe. Good thing there are standard Valve implementations available that do just what I needed.

Just drop the next snippet somewhere appropriate:

 
         <!-- Enable http request/response logging.--> 
        
         < 
         Valve 
         className 
         = 
         org 
         .apache.catalina.valves.RequestDumperValve 
        
         prefix 
         = 
         localhost_access_log 
         . suffix=.log 
        
         pattern 
         = 
         common 
         directory=${jboss.server.home.dir}/log 
        
         resolveHosts 
         = 
         false 
         />

Appropriate in my case was in the file “[JBOSS-HOME]/server/default/deploy/jboss-web.deployer/server.xml”.

And lo and behold it logged:

 
         11:46:44,262 INFO  [[localhost]]           authType=BASIC 
        
         11:46:44,262 INFO  [[localhost]]      contentLength=48189 
        
         11:46:44,262 INFO  [[localhost]]        contentType=application/pdf 
        
         11:46:44,262 INFO  [[localhost]]             header=Pragma=public 
        
         11:46:44,262 INFO  [[localhost]]             header=Cache-Control=maxage=3600 
        
         11:46:44,262 INFO  [[localhost]]             header=Expires=Thu, 01 Jan 1970 01:00:00 CET 
        
         11:46:44,262 INFO  [[localhost]]             header=X-Powered-By=Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0 
        
         11:46:44,332 INFO  [[localhost]]             header=X-Powered-By=JSF/1.2 
        
         11:46:44,332 INFO  [[localhost]]             header=X-Powered-By=Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0 
        
         11:46:44,332 INFO  [[localhost]]             header=X-Powered-By=JSF/1.2 
        
         11:46:44,332 INFO  [[localhost]]             header=Content-Type=application/pdf 
        
         11:46:44,332 INFO  [[localhost]]             header=Content-Length=48189 
        
         11:46:44,332 INFO  [[localhost]]             header=Date=Thu, 26 Aug 2010 09:46:44 GMT 
        
         11:46:44,332 INFO  [[localhost]]            message=null 
        
         11:46:44,332 INFO  [[localhost]]         remoteUser=admin 
        
         11:46:44,332 INFO  [[localhost]]             status=200

补充参数说明：

其中具体配置参数如下所示：

`className`	实现的Java类名。必须被设置成org.apache.catalina.valves.AccessLogValve。
`directory`	存放日志文件的目录，可以是相对路径或者绝对路径。如果使用相对路径，是指相对于 $CATALINA_HOME的路径。如果不指定directory属性，缺省值是“logs”（相对于 $CATALINA_HOME）
`pattern`	需要记录的请求/响应不同信息域的格式布局。如果是“common”或者“combine”，说明选择标准格式。下面会有关于配置这个属性的更多信息。
`prefix`	日志文件名的前缀。如果没有指定，缺省值是“access_log.”。如果不想使用前缀，使用长度为0的字符串。
`resolveHosts`	将远端主机的IP地址通过DNS查询转换成主机名，设为true。如果为false，忽略DNS查询，报告远端的IP地址。
`suffix`	日志文件名的后缀。如果没有指定，缺省值是“”。如果不想使用后缀，使用长度为0的字符串。
`rotatable`	缺省值为true，用来决定日志是否翻转的标志。如果为false，日志文件永远不翻转，并且忽略fileDataFormat。要谨慎使用。
`condition`	打开条件日志。如果设置了这个属性，只有在ServletRequest.getAttribute()是null的时候，才会为请求创建日志。比如，如果condition设为junk，则只有在Servlet.getAttribute("junk")==null的时候，才会记录这个请求。使用过滤器，可以很容易设置（或者取消设置）不同请求的属性。
`fileDateFormat`	允许在日志文件名称中使用定制的日期格式。日志的格式也决定了日志文件翻转的频率。如果想每个小时翻转一次，将这个值设为yyyy-MM-dd.HH