If you want to force the browser to reload the login file, you need to send the 
301 redirect response instead of sending the request to login url.

BTW, please use [email protected] to ask the camel usage question.

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) 
(English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On December 17, 2013 at 5:04:14 PM, yudiao123 ([email protected]) wrote:
>  
> if I do as below : the context can route to index.jsp,but the url  
> on browser
> the url is not change.so the context in index.jsp can not use.  
> public void configure() {
>  
>  
> from("jetty:http://192.168.0.154:8181/?matchOnUriPrefix=true";)  
> .process(new Processor() {
> public void process(Exchange exchange) throws Exception {  
> sessionId =
> exchange.getIn(HttpMessage.class).getRequest().getRequestedSessionId();  
> if (null==sessionId)
> {
> exchange.getIn().setHeader("sessionId", 0);;
>  
> exchange.getIn().setHeader(Exchange.HTTP_BASE_URI,
> constant("http://192.168.0.154:8181/uiserver/index.jsp";));  
> exchange.getIn().setHeader(Exchange.HTTP_PATH, constant(""));  
> exchange.getIn().setHeader(Exchange.HTTP_SERVLET_REQUEST,  
> constant(""));
> exchange.getIn().setHeader(Exchange.HTTP_URI,
> constant("http://192.168.0.154:8181/uiserver/index.jsp";));  
> }
> else
> {
> exchange.getIn().setHeader("sessionId", sessionId);;  
> exchange.getIn().setHeader(Exchange.HTTP_URI,
> constant("http://192.168.0.154:8181/uiserver/index.jsp";));  
> }
> }
> })
>  
> /* .process(new Processor() {
> public void process(Exchange exchange) throws Exception {  
> exchange.getOut().setHeader(Exchange.HTTP_URI,
> constant("http://www.google.com";));
> }
> })*/
> .to("ahc:http://127.0.0.1:8181/uiserver/thinknet/index.jsp";);  
>  
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/can-camel-used-for-Single-Sign-On-tp5744926p5744928.html
>   
> Sent from the Camel Development mailing list archive at Nabble.com.  
>  

Reply via email to