On Mon, 23 Oct 2006, Jan Korbel wrote:
I'm testing latest stable version of RT (3.6.1) about a week and i have a
problems with HTTPS only site. When i want to update ticket, data is sent but
browser wanna go to URL:
https://mysite.tld:80/Ticket/Display.html?id=1
Set($WebPort , 443);
Set($WebBaseURL , "https://mysite.tld";);
Another strange thing is name of cookie:
RT_SID_SITE.80
From share/html/Elements/SetupSessionCookie:
my $cookiename = "RT_SID_".$RT::rtname.".".$ENV{'SERVER_PORT'};
Only one HTTPS configuration, which is going fine so far, is RT/HTTP and
mod_proxy in Apache with HTTPS ;) I know it's not so nice, so if you have
some idea, write it.
You are running RT on port 80, but then forwarding port 443 to
port 80 using mod_proxy? Why not just run RT on port 443 directly?
I wonder if changing the SERVER_PORT line in
lib/RT/Interface/Web.pm to use the hard coded $WebPort would fix it for
you?
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
