(Sorry for top posting, my MUA does not somehow allow posting properly in *this* message)

It is the Apache that does the redirection request for browser. This has nothing to do with the fact that it only handles http sockets. If Apache does not do it, nothing does.

br. jarif

brendan kearney kirjoitti 18.1.2016 15:29:

I am not understanding this.  Apache is doing nothing with https.  The https is being handled on the load balancer and everything apache sees is http only.

 

Does that mean the load balancing needs to be changed?

On Jan 18, 2016 4:45 AM, "Thomas Bruederli" <thomas@roundcube.net> wrote:

On Mon, Jan 18, 2016 at 1:55 AM, Brendan Kearney <bpk678@gmail.com> wrote:
> i have 2 apache instances behind HAProxy, where HAProxy is running the HTTPS
> and load balancing to RCM in the clear.  i have set the 'use_https' option
> to true, and it works in most cases.  i have found an exception and i wanted
> to see if this has been fixed in more recent versions.
>
> if i browse to https://host.domain.tld/roundcubemail (note https, with no
> trailing slash), i am redirected to
> http://host.domain.tld/roundcubemail/ (note not https, with trailing slash).
>
> if i correct the http:// to https:// everything works and all pages are
> secured.  it seems that only the redirect to the URI with the trailing slash
> is where this comes up.

The redirect from /roundcubemail to /roundcubemail/ is done by Apache
and doesn't yet hit Roundcube and its use_https logic. Thus not a
Roundcube issue and nothing we could fix on our side. You need to
teach Apache to redirect to https.

~Thomas
_______________________________________________
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

_______________________________________________
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

-- 
jarif.bit