[thelist] CF: FormURL2Attributes Bug/Question

[Daniel J. Cody]

-------- Original Message --------
Subject: Re: [thelist] CF: FormURL2Attributes Bug/Question
Date: Mon, 04 Feb 2002 08:51:54 -0600
From: "Daniel J. Cody" <djc at members.evolt.org>
Newsgroups: evolt
References: <p05001903b88441773744@[192.168.232.2]>

Hey Frank -

What version of CF are you using?

This was an issue back with CF 4.5.1 - it wasn't returning all of the
apache CGI vars(which seems to be your prob). I ended up having to edit
and recompile the coldfusion module to have it recognize cgi.path_info
and a couple other vars.

by default, CF(on linux) is only configured to return:
AUTH_TYPE, CONTENT_LENGTH, CONTENT_TYPE, PATH_INFO, PATH_TRANSLATED,
QUERY_STRING, REQUEST_URI, REMOTE_ADDR, REMOTE_HOST, REMOTE_USER,
SCRIPT_NAME, SERVER_NAME, SERVER_PORT, SERVER_PROTOCOL, SERVER_SOFTWARE,
              REQUEST_METHOD, HTTP_REFERER, HTTP_USER_AGENT

from apache. so REDIRECT_QUERY_STRING for example, wouldn't be in the
CGI scope(or whatever its called) that CF returns unless you *manually*
add it and recompile the CF module. this, afaik, is a CF bug. or
'feature' if thats whatcha wanna call it :)

anyways, to answer your question, the Fusebox tag relies on the
REQUEST_URI variable so you'll have to add that enviornment variable to
the module and recompile it because at the time, CF didn't recognize
REQUEST_URI by default, although in 4.5.1SP2 and up, it does.

that may sound a bit wacky, but its early and i haven't had enough
coffee, shout if you have questions :)

.djc.


Frank wrote:

 >
 > I've got a situation whereby when using the Fusebox tag
 > FormURL2Attributes.cfm (1.0b1)for the feature of creating search
 > engine friendly urls, that it works perfectly on my Win2k box running
 > apache, but fails on my Linux server running the same version of CF
 > and Apache. More specifically, it it will translate a URL or Form
 > variable to an attribute on the PC side, but won't on Linux.
 >
 > Does anyone have experience with having run into this? What was your
 > solution?