Sorry that's a Typo error. The Loggin IN interceptor is not capturing anything in the log file when the request comes from URL-2. But the request is fully logged when the request comes from URL-1.
The response message is the same from URL-1 and URL-2. Is that Phase.PRE_PROTOCOL is the right phase to deal this? Freeman-2 wrote > Is there any difference between the authenticating and non-authenticating > message? > Btw, you add MyInterceptor but your code is SpaSoapInterceptor, I guess > it's a typo, right? > > －－－－－－－－－－－－－ > Freeman(Yue) Fang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://fusesource.com | http://www.redhat.com/ > Twitter: freemanfang > Blog: http://freemanfang.blogspot.com > http://blog.sina.com.cn/u/1473905042 > weibo: @Freeman小屋 > > On 2013-1-7, at 下午4:41, jbright wrote: > >> I do have Logging IN and OUT interceptors configured... >> >> > <jaxws:inInterceptors> >> > <ref bean="myInterceptor" /> >> > <ref bean="logInbound" /> >> > </jaxws:inInterceptors> >> > <jaxws:outInterceptors> >> > <ref bean="saajOutInterceptor" /> >> > <ref bean="logOutbound" /> >> > </jaxws:outInterceptors> >> >> The myInterceptor is defined like this: >> >> > <bean id="myInterceptor" class="com.......util.MyInterceptor" /> >> >> The MyInterceptor.class extends AbstractSoapInterceptor >> >> public SpaSoapInterceptor() { >> super(Phase.*PRE_PROTOCOL*); >> getAfter().add(SAAJInInterceptor.class.getName()); >> } >> >> in the handleMessage (... ) method I do the LDAP authentication part. >> >> >> >> >> >> -- >> View this message in context: >> http://cxf.547215.n5.nabble.com/Interceptor-Issue-Https-to-Http-tp5721102p5721119.html >> Sent from the cxf-user mailing list archive at Nabble.com. -- View this message in context: http://cxf.547215.n5.nabble.com/Interceptor-Issue-Https-to-Http-tp5721102p5721124.html Sent from the cxf-user mailing list archive at Nabble.com.
