<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>RE: [rt-users] RT - SSL - Create/Resolve issue</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Charles,<BR>
<BR>
If everything is working fine, up until shortly after you "Submit" the newly created ticket, then the issue is in your RT_SiteConfig (or RT_Config) in ~/rt-dir/etc/.<BR>
<BR>
In there is a specification of the URL used by RT, including the "http[s]" and "URL:port" component. So you need to set these to use HTTPS and 443. You should find things work fine then.<BR>
<BR>
I am prompted to ask Jesse a question at this point.... why does RT use explicit links, such that the above issue occurs, why is it that when a ticket is created it doesn't just refer to the relative link?<BR>
<BR>
Regards,<BR>
BenR<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: rt-users-bounces@lists.bestpractical.com on behalf of Charles Kugelman at HQ<BR>
Sent: Fri 9/30/2005 1:58 AM<BR>
To: rt-users@lists.bestpractical.com<BR>
Subject: [rt-users] RT - SSL - Create/Resolve issue<BR>
<BR>
We are having an issue with RT and SSL:<BR>
<BR>
<BR>
<BR>
When using SSL, we are being presented with a "page cannot be displayed"<BR>
upon create/resolve of tickets. This happens immediately after the<BR>
"create" or "update ticket" button is clicked. If the user clicks the<BR>
back button and makes another attempt to send the create or update<BR>
request it then completes successfully.<BR>
<BR>
<BR>
<BR>
I've checked the error logs of Apache and RT; nothing is generated when<BR>
this occurs.<BR>
<BR>
<BR>
<BR>
#start httpd.conf snip<BR>
<BR>
<BR>
<BR>
#This is how we setup <A HREF="http://rt.domain.com">http://rt.domain.com</A> <<A HREF="http://rt.domain.com/">http://rt.domain.com/</A>> to<BR>
redirect to <A HREF="https://rt.domain.com">https://rt.domain.com</A> <<A HREF="https://rt.domain.com/">https://rt.domain.com/</A>> .<BR>
<BR>
#I'm sure there is a better way of doing this, any suggestions?<BR>
<BR>
#Could this be the problem?<BR>
<BR>
<VirtualHost ip.ad.re.ss:80><BR>
<BR>
ServerName rt.domain.com<BR>
<BR>
ServerAdmin rtadmin@domain.com<BR>
<BR>
DocumentRoot /opt/rt/share/html/redir #The index.html is an<BR>
instant redir to the https site.<BR>
<BR>
</VirtualHost><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
LoadModule ssl_module libexec/libssl.so<BR>
<BR>
Listen 443<BR>
<BR>
<BR>
<BR>
<VirtualHost ip.ad.re.ss:443><BR>
<BR>
ServerName rt.domain.com<BR>
<BR>
ServerAdmin rtadmin@domain.com<BR>
<BR>
DocumentRoot /opt/rt/share/html<BR>
<BR>
SSLEngine on<BR>
<BR>
SSLCertificateFile /usr/local/apache/conf/ssl.key/server.crt<BR>
<BR>
SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key<BR>
<BR>
AddDefaultCharset UTF-8<BR>
<BR>
PerlModule Apache::DBI<BR>
<BR>
PerlRequire /opt/rt/bin/webmux.pl<BR>
<BR>
<Location /><BR>
<BR>
SetHandler perl-script<BR>
<BR>
PerlHandler RT::Mason<BR>
<BR>
</Location><BR>
<BR>
</VirtualHost><BR>
<BR>
<BR>
<BR>
#end httpd.conf snip<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Thanks in advance.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Charles Kugelman<BR>
<BR>
Network Administrator<BR>
<BR>
ITT Educational Services, Inc.<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>