From: Roberto S. G. <roberto.santos@un...> - 2005-10-13 09:09:38
thanks for your quick reply.
Related to SSL issues, may be there's a very little thing to take care of :
If I set the "logout page" url, and the domain (before the first slash)
is "exactly the same" as where webmail resides, (if it's a different
domain, there's no problem), even if it's set as: "http://domain";, the
browser load that page as https... and that's not what we want: we'd
like it to be http.
It's very strange, I know... sorry if it's not a squirrel issue... may
be I'm doing something wrong, or it's something related to ssl+http
header issues, as seen in signout.php:
header('Status: 303 See Other');
thanks for your time.
>Hello Roberto S. G.,
>On Monday, October 10, 2005, you wrote:
>>> We've been using squirrelmail for years, and now we have an SSL
>>> appliance between the apache server and the final users... the SSL
>>> appliance does the https encryption to users, and apache always servers
>>> http... :
>>> (web server):80 <-------> (SSL appliance):443 <-------> user
>>> Maybe this configuration is used at other sites.
>This has come up fairly recently on the users list, and I took some
>ideas to the development list. I've unfortunately been snowed under
>with some other things recently so I've not had a chance to look into
>this, but my plans are to allow the site admin the ability to set an
>address in the config that PHP defaults to if set. This will allow you
>to pre-define your https url so we don't have to try and guess what it
>is. As you have found out in your situation, your SSL appliance is
>doing all the ssl stuff while feeding the actual web servers an http
>connection. This causes issues in php applications (or any that
>attempt to detect ssl) because the information provided by apache says
>it is http, and port 80... that is unfortunately the fact.
>I'm going to see about working on the forced url stuff this week, and
>get a patch up for people to play with.