Is Coldfusion 9 truncating my URL after the first parameter?

[Mark Mongeau]

Hi,

I am running CF9 standard on a production environment. We had a disk crash this week and had to rebuild our server as the backup was corrupted as well.

I installed IIS and CF 9, and now have an issue with query stringd being truncated.

These are short strings that were working before the crash

This is causing errors as values the cold fusion pages are looking for are not being provided to the pages.

Here is an example of a truncated URL from the IIS log:

redirectionNom=164666-events.html&

the correct url would be  redirectionNom=164666-events.html&id2=23456

Note the ampersand where other data would be added to the url.

I have validated that this is the issue by dumping out the values for the url and the CGI variables and comparing this to the url in the address bar. We are definitely losing things off of our URLs.

These are not very long query strings, so request filtering should not be stopping them, and we are not getting the expected 404 error we would get if it was a request filtering issue.

I understand that there was a new security feature added to CF to limit the query string to 100 parameters.

I don't think that this new feature us the problem. I have been programming CF since CF 3.0 and have never had an issue like this

Can any one help please?

Thanks in advance!!

Mark Mongeau

[BKBK]

Please bear with me. It is unclear to me what the actual problem is.

Is this a problem about the IIS log? Do you mean that the user navigates, without any problem, to a URL whose query-string is redirectionNom=164666-events.html&id2=23456, whereas the IIS log only registers redirectionNom=164666-events.html& ?

Alternatively, is there a difference between the information the browser sends and the information in the server's memory? In other words, does the user navigate, without any problem, to a URL whose query-string is redirectionNom=164666-events.html&id2=23456, whereas the relevant variables in URL and CGI scope only contain redirectionNom=164666-events.html& ?

[Mark Mongeau]

Hi BKBK,

No the issue is, that the user is not able to navigate to the URL. Instead they get a CF error that the value is not in the scope even though it should be, and was before the server crash and rebuild.

The query string is fully present in the browser's address bar.

The querystring is truncated in :

• The IIS Log
• The CGI scope in Coldfusion
• The URL scope in Coldfusion.

Pages that are expecting the url value are failing because the value is not available to the page because of the truncation.

.

Let me know if you need more information

Thanks for your reply,

Mark

[BKBK]

The word redirectionNom suggests you may have implemented URL redirection. If so, then this IIS URL redirection fix could help.

[Mark Mongeau]

Hi BKBK,

I am using URL redirection. However I am using ISAPI_REWRITE from Helicon. And the version is the same and the re-write rules are the same.

I think that it is an IIS config item but not the redirect as it is not being used. Any other suggestions would be greatfully investigated.

Thanks

Mark

[tribule]

Mark, can you run a HTTP trace and see what HTTP status code you get back when you visit the correct URL? Is there a redirect of any type occuring?

[Mark Mongeau]

Hi Tribute:

Here is an image of the trace where the URL gets changed.

As you can see there is some information added and some changed. Unfortunately I cannot access all of the CF code as some was compiled to Java byte code.

I came in after the site was (poorly) written and while I have been able to work some miracles with the code this one has me stumped.

Note thet the rewrite code in ISAPI_REWRITE is the same as it was on the old production server, and it worked there.

Thanks

Mark

[Mark Mongeau · Accepted solution]

So I fgured it out from the trace. I had looked at and compared the httpd.conf files for ISAPI_REWRITE but obviously did this while I was asleep. There was a ruke missing in the production file hence the screw up. Thanks everyone for your help!!

Mark

[BKBK]

That is how things sometimes go. Thanks for sharing the solution with us.

[tribule]

Good stuff. It sounded like a URL rewrite issue.