Fri, 10 Apr 2026 18:48:32 +0000 https://bugs.horde.org/ticket/8515 Switching http protocols during session breaks URL generation. Switching from https -> http or the reverse causes full url generation to break: The default value for $conf[server][port] is $_SERVER[SERVER_PORT], so once you login under https the value is set to 443. If you then switch protocols, since the config is cached in the session, that value is now wrong. Not sure of the correct fix, but I'm thinking maybe we need to set the value of conf[server][port] on every page load in Registry::importConfig()? Fri, 21 Aug 2009 00:57:33 +0000 https://bugs.horde.org/ticket/8515#t55503 Why would you want to switch protocols anyway? There is one place where we already do this, so it's possible: you can use HTTPS for login only. Fri, 21 Aug 2009 07:30:28 +0000 https://bugs.horde.org/ticket/8515#t55504 I had always assumed this was by design (not being able to do this) due to my own experience with it. While helping someone in IRC, however, I had told them it was not possible to switch mid-session and was told by Chuck that it should be possible unless secure cookies were enabled. Once I knew it *should* be possible, I was able to track down what was causing the weird behavior. This also bites me *all* the time when I have a Horde window open (I always use https, but do not force it) to upload images, or author a blog entry, then try to view my horde-driven website, or any other page with horde-generated embedded content. The links are always broken because they contain the wrong port number for the protocol being used. Fri, 21 Aug 2009 13:39:02 +0000 https://bugs.horde.org/ticket/8515#t55513 How about simply leaving the default empty? Fri, 21 Aug 2009 13:46:39 +0000 https://bugs.horde.org/ticket/8515#t55515 Well, that was easy :) Setting the default value to an empty string seems to fix things...so I guess we should change that to the default? Fri, 21 Aug 2009 14:00:24 +0000 https://bugs.horde.org/ticket/8515#t55516 Makes sense to me. This should also simplify the url building in Horde:: a lot, because we only have to tackle the port if it is set in the configuration. Fri, 21 Aug 2009 14:33:08 +0000 https://bugs.horde.org/ticket/8515#t55519 Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/horde/config/conf.xml?rt=horde&r1=1.275&r2=1.276&ty=u Wed, 02 Sep 2009 03:14:10 +0000 https://bugs.horde.org/ticket/8515#t55639 Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/horde/config/conf.xml?rt=horde&r1=1.74.2.86&r2=1.74.2.87&ty=u Wed, 02 Sep 2009 03:14:41 +0000 https://bugs.horde.org/ticket/8515#t55640