According to the log, it redirected fine: 2010-08-24 08:26:28,803 DEBUG [org.springframework.webflow.mvc.servlet.FlowHandlerAdapter] - <Sending external redirect to 'http://portal-integration. .../app1/?ticket=ST-1-swPSczPj4FLUDIDfiN7m-portal-integration....'>
If you use Firefox, this plugin can help capture the headers, and all of the redirects: https://addons.mozilla.org/en-US/firefox/addon/3829/ On Tue, Aug 24, 2010 at 2:53 AM, Felix Schumacher < [email protected]> wrote: > On Mon, 23 Aug 2010 15:38:16 -0400, Scott Battaglia > <[email protected]> wrote: > > I've never seen that behavior before and it shouldn't be happening (we > > rely on the service url passed in and essentially send it back > unmodified > > except for the appending of the ticket). > > > > If you turn up DEBUG logging in CAS for CAS itself and potentially Web > > Flow, does it give any more insights? > I have turned up logging to DEBUG for org.springframework.webflow, > org.jasig and (very probably overkill) org.jasig.cas.web.flow. Attached is > the debugging output when trying to log into app1. Every reference to that > app is logged with http://portal.../app1/. Still the end result is me > visiting https://portal.../app1/. > > The logs are generated with a slightly modified login-webflow.xml. That > was done to work around the bug with post redirect views. Alas changing the > webflow to the original 3.4.2 configuration didn't change the outcome. > > In the logs are references to realserver. That is the name of the server > on which app1 is located. The setup for the whole environment is as > follows: > > loadbalancer (name portal...) > | > ___httpd____ > / \ > tomcat1 tomcat2 (name realserver) > | | > cas-server app1 > > Anything else I could try? > > Bye > Felix > > > > On Mon, Aug 23, 2010 at 4:54 AM, Felix Schumacher wrote: > > Hi, > > > > if the cas server and an application are on the same server (well > > domain > > name), the login sequence seems to update the protocol of the > > application > > to https. > > > > I am using version 3.4.2 (will update to 3.4.2.1 soon). The cas server > > is > > placed under https://portal-integration. [2].../cas-server. > > > > If I call app1 - which is configured to be on the same domain name - > > like > > http://portal-integration. [3].../app1/, the browser will get > > redirected > > correctly to > > https://portal-integration. > > [4].../cas-server/login?service=http%3A%2F%2Fportal-integration... > > The cas-server now redirects it back to > > *https*://portal-integration..../app1/. > > > > This is not what I want. > > > > If on the other hand I try an application with a different domain name > > like http://otherserver. [5]..:8080/app2/ the following redirects take > > the > > browser correctly to *http*://otherserver...:8080/app2/. > > > > I have attached those two cases as a slightly shortened firefox > > live-header protocol. > > > > Is this a known bug, or a wanted feature? > > > > Bye > > Felix > > -- > > You are currently subscribed to [email protected] [6] as: > > [email protected] [7] > > To unsubscribe, change settings or access archives, see > > http://www.ja-sig.org/wiki/display/JSG/cas-user [8] > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
