Hi, You need elaborate how your customer interceptor to do the authentication stuff, using http basic auth, ws-security UsernameToken, or something else?
If the authentication works when you directly access the URL-1 but not through URL-2, you may need dump the unwire message URL-1 receiving and compare the two(directly and through URL-2) to see the difference, if you use http basic auth, which means the username/password stored in http header, so router through URL-2 might change/remove those headers. －－－－－－－－－－－－－ 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 下午3:21, jbright wrote: > I've created custom interceptor to intercept the service request, whereas the > service operation is deployed in the server with the URL as below: > > *URL-1* http://abc.com/abcApp/services/abcbusiness > > since this is the real server, the requests for the internet enabled > applications are not allowed to hit this direct URL. > > The network team had provided another URL which the internet applications > can hit to access the services from the abcApp, that's like below: > > *URL-2* https://abc-dmz.com/abcApp/ServicesOfabcBusiness > > They say this is just an URL mapping, any request to URL-2 will get routed > to the URL-1 > > Unfortunately, the service is not getting intercepted to do the > authentication stuff implemented thru the interceptor, but the service is > responding with the data requested ... ... > > how to deal this ? > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Interceptor-Issue-Https-to-Http-tp5721102.html > Sent from the cxf-user mailing list archive at Nabble.com.
