RT4 query builder not decoding parameters from URL

RT Users
1

I have a fresh install of RT 4.0.5 on a new server. I pointed this new instance to an existing RT 4.0.2 database (after running the db upgrade script).
The problem I am having is that the query builder:
Existing saved searches execute with no problems. All new searches end-up URL encoded, thus fail to run and “0 results” are returned. For example, a search like ‘id = 12345’ is getting executed as ‘id%20%3D%2012345’.
Once the query executes and returns nothing, a click on “Advanced” from the results page will show the query and format as URL encoded strings… nothing is getting decoded before execution.
Configuration (Apache conf and RT_SiteConfig) are the same.
Any ideas? I am completely at a loss.

2

Hi,

I’m having this same problem or at least an extremely similar one. Were you
ever able to solve this?

Thanks!
Daniel Farst
IT Support Coordinator
College of Arts and Sciences
Case Western Reserve University

daniel.farst@case.eduOn Tue, Mar 27, 2012 at 2:12 PM, JP White jpwhite@hotmail.com wrote:

I have a fresh install of RT 4.0.5 on a new server. I pointed this new
instance to an existing RT 4.0.2 database (after running the db upgrade
script).

The problem I am having is that the query builder:

Existing saved searches execute with no problems. All new searches end-up
URL encoded, thus fail to run and “0 results” are returned. For example, a
search like ‘id = 12345’ is getting executed as ‘id%20%3D%2012345’.

Once the query executes and returns nothing, a click on “Advanced” from
the results page will show the query and format as URL encoded strings…
nothing is getting decoded before execution.

Configuration (Apache conf and RT_SiteConfig) are the same.

Any ideas? I am completely at a loss.

3

I am also getting a similar issue. Has anyone gotten this problem resolved?

4

Which version of RT?>

5

The RT version that I am using is Version 5.0

6

In reviewing the problem , it seems that the query was return https URL rather that http. So I just had to install SSL on the web server. That solved the issue that I was experiencing.

The challenge was that the error message was not clear. There was nothing being reported in the logs and I had configured the WebPort to 80