Crazy suggestion, but if you convert the form method from POST to GET, the 404 handler in IIS will pass the old query string in the new query string:
CGI.query_string ---> 404;http.....?old_query_string On Thu, Apr 2, 2009 at 2:27 PM, David McGuigan <davidmcgui...@gmail.com>wrote: > > Thanks for the suggestion. I do realize that ISAPI rewriting is an > alternative, but my entire application controller is just a CF-based, > dynamic translation and coordination of URLs to content, so I want to > handle > that with CFML logic, and not have to maintain it extraneously. > Any Java fiends out there that can give me some Java methods to try to > output the raw HTTP signature handed down to ColdFusion? > > > On Thu, Apr 2, 2009 at 12:22 PM, Ben Nadel <b...@bennadel.com> wrote: > > > > > Ooooh, you're using 404 handling. Gotcha. Yeah, I use that on my site a > > lot. > > I am not sure that I have ever submitted a FORM to it. > > > > You might want to look into something like ISAPI_REWRITE which I think > > changes the URL in a more natural way. > > > > > > On Thu, Apr 2, 2009 at 2:14 PM, David McGuigan <davidmcgui...@gmail.com > > >wrote: > > > > > > > > NP Ben, I was just confused. So you actually don't have to configure > any > > > URL > > > rewriting with IIS 6+. You just grab the site, update the 404 custom > > error > > > handler to use a URL ( Like "/index.cfm" ), and then change the feature > > > settings mode to "custom errors". It'll then pass everything through to > > the > > > CF template you specify. From there on I'm just dumping things on that > > > template, and neither FORM, or the result of GetHTTPRequestData are > > > populated, > > > which is the real issue. > > > > > > I'm guessing it's just that CF isn't parsing the (potentially new) IIS > 7 > > > format of custom error passthrough correctly, similar to how PHP > > struggles > > > with it as described here: http://bugs.php.net/bug.php?id=38094 > > > I've just filed the bug with Adobe. We'll see what they say, maybe > > there's > > > some workaround. > > > > > > > > > > > > 2009/4/2 Jason Fisher <ja...@wanax.com> > > > > > > > > > > > At its most basic, GET will populate the URL scope, POST will > populate > > > the > > > > FORM scope. Is there a reason you can't look to the FORM scope > during > > > > processing? > > > > > > > > > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:321249 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4