Ok, I'm at a total loss here. I've got an IHS web server that is
protected by Siteminder. The first time you attempt to get a
restricted page, it redirects you to the login page. Below are the
exact headers being sent back by the web server (as captured by Web
Detective):

HTTP/1.1 302 Found
Server: IBM HTTP Server/V5R3M0
Date: Fri, 17 Sep 2004 20:16:17 GMT
Location: https://www.mysite.com/siteminderag...EASON=0&TARGET=$S
 M$http%3a%2f%2fwww%2emysite%2ecom%3a7070
%2fservlet%2fJNDI2%2frestricted%2fSn
oopServlet
Connection: Keep-Alive
Accept-Ranges: bytes
Content-Type: text/html
Content-Length: 527
Last-Modified: Fri, 17 Sep 2004 20:16:17 GMT
HTTP_sm_transactionid: 35e73271-40000e3-414b4612-02e7-0a7f45f4
HTTP_sm_realm: Protect 7070 - secwas
HTTP_sm_realmoid: 06-3d345281-095c-0020-0000-29b1000029b1
HTTP_sm_sdomain: .mysite.com
HTTP_sm_authtype:
Via: 1.1 xxx.xxx.xxx.xxx (Alteon iSD-SSL/3.1.6.8)


(note the site DNS name and IP address were changed)

You can see from the Location header that the redirect is to
https://www.mysite.com/.... but the browser's next request is for
http://www.mystite.com/.... Both IE and Mozilla behave the same way
here (although wget works fine and goes after https next).

Can anyone see anything wrong with the headers above that would cause
the redirect to use the wrong protocol???

-Norm

[ Post a follow-up to this message ]

Norman,

Hopefully you've solved this since... but in case you haven't - check
to make sure that your Forms Authentication Scheme in SiteMinder is
directed to the SSL port. If you set it up originally under non-SSL,
you may have forgotten to change it?

Good luck,
Rob

deflatermouse@hotmail.com (Norman Ackroyd) wrote in message news:<13ce2235.0409200511.3dc998
dc@posting.google.com>...
> Ok, I'm at a total loss here. I've got an IHS web server that is
> protected by Siteminder. The first time you attempt to get a
> restricted page, it redirects you to the login page. <snip>

> You can see from the Location header that the redirect is to
> https://www.mysite.com/.... but the browser's next request is for
> http://www.mystite.com/.... Both IE and Mozilla behave the same way
> here (although wget works fine and goes after https next).
>
> Can anyone see anything wrong with the headers above that would cause
> the redirect to use the wrong protocol???
>
> -Norm

[ Post a follow-up to this message ]