Hi All, I thought it was a bug of cas server 3.2, would you check it for me?

[Ding Kai-Jian]

No, I didnot modify any file.
I just deploy CAS 3.1 M2 on tomcat, And enable 8443 port.
I use tomcat 5.5&jre 1.5.0_06 on windows platform.
My client is Apache2:AuthCAS found from cpan, which works perfictly with CAS 
3.07.
I find something from log.
When the client get url http://localhost/web1?service=ST-130-
AcfthfcYZfhpUv5v1k5hNnWVgy6oViSMcPn-20
, the client can not find param ticket and can not set a cookie, and will 
redirect 
to https://localhost:8443/cas/login?service=http://localhost/web1?service=ST-
130-AcfthfcYZfhpUv5v1k5hNnWVgy6oViSMcPn-20 and the server will add another 
service param at the end. And then a loop start.
When I enable log to debug level for server, I find somehing strange.It looks 
like:

all above is success
......
[org.jasig.cas.CentralAuthenticationServiceImpl] - Granted service ticket [ST-1-
OmdWleMTjfxfbZtrjEnBihhdR4acFSa7Kwd-20] for service [http://localhost/web1] for 
user [d]
[org.jasig.cas.web.flow.WarnAction] - Action 'WarnAction' completed execution; 
result is 'redirect'
[org.jasig.cas.web.flow.ExtractServiceAction] - Action 'ExtractServiceAction' 
beginning execution
[org.jasig.cas.web.flow.ExtractServiceAction] - Placing service in FlowScope: 
http://localhost/web1?service=ST-1-OmdWleMTjfxfbZtrjEnBihhdR4acFSa7Kwd-20
[org.jasig.cas.web.flow.ExtractServiceAction] - Action 'ExtractServiceAction' 
completed execution; result is 'success'
......
[org.jasig.cas.web.flow.TicketGrantingTicketExistsAction] - 
Action 'TicketGrantingTicketExistsAction' completed execution; result 
is 'ticketGrantingTicketExists'
......

It seems that the server did generate url using service instead of ticket at 
ExtractServiceAction.