Hi, Emmanuel.
What kind of protocol do you use (httpS it seems). What is your settings
in RT_SiteConfig.pm for WebPort/WebBaseURL (those settings changed
between RT 3.6 and RT 3.8).
# THE WEBSERVER:
Set($WebPath , /rt);
Set($WebBaseURL , http://rt.pop-sp.rnp.br;);
Maybe you were previously
Hi, folks.
I have faced a problem when I'm using Request Tracker:
Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
On Mon, Jan 11, 2010 at 06:13:25PM -0200, Wagner Pereira wrote:
Hi, folks.
I have faced a problem when I'm using Request Tracker:
Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled
Hi everyone,
I'm getting the dreaded Bad Request/HTTP 400 at logout. My
RT_SiteConfig.pm is below, and I'm using fcgid. Any suggestions?
-C-
-
Set($rtname, 'sclrev.org');
Set($Organization, 'sclrev.org');
Set($CorrespondAddress , '[EMAIL PROTECTED]');
Set($CommentAddress , '[EMAIL
Chris Haumesser wrote:
Hi everyone,
I'm getting the dreaded Bad Request/HTTP 400 at logout. My
RT_SiteConfig.pm is below, and I'm using fcgid. Any suggestions?
Nevermind, just needed to clear my browser cache. D'oh. Sorry for the
spam.
