Perhaps this is a feature request, but:
My production site is using url rewriting, so the actual url is resolved into the cgi.path_info or xajp-path-info variables, which means every request shows as /index.cfm or /rewrite.cfm
I can always click in to look at the request headers to see what the actual request was, however, it means I mostly only see these two as page requests; this is especially troublesome in reviewing log files.
Is there a setting, or better way for me to be doing this?
--
You received this message because you are subscribed to the Google Groups "FusionReactor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fusionreacto...@googlegroups.com.
To post to this group, send email to fusion...@googlegroups.com.
Visit this group at http://groups.google.com/group/fusionreactor.
For more options, visit https://groups.google.com/groups/opt_out.
I'm rewriting with IIS Url Rewrite 2.0, not at the tomcat stage, and for future reference the application in question is running the cfwheels framework.
Was FR-3663 (feature request you mentioned above) included in the v5 release? I do not see any documentation how to configure a re-writer tool like Tuckey.
I was looking here for help:
http://docs.intergral.com/display/FR50/Home
Thoughts?
Scott
Can someone suggest a url rewritten setup of any kind with tomcat + railo & FR where the requested rewritten url shows up properly in FR ?
Jonathan, since you refer to xafp-path-info appearing, I think that may be coming from the boncode connector (the IIS connector for Tomcat that was created by Bilal Soylu and is often used with Railo rather than the native Tomcat connector). If so, I wonder if that’s playing a part here and if perhaps something in its configuration can help you. Have you talked to either him or others on that or the Railo team?
I know you’re asking here on the FR list because you’re finding it’s an issue for you in FR, and I appreciate that you’ll really want an answer from someone on the Intergral engineering team. I hope they may chime in here.
But while you wait, I was wondering if this may help you get somewhere. Also, I’m curious: what do you see if you do a dump of the CGI scope? I’d not be surprised if the boncode connector might pass in something that would appear there (integrated as it is with CFML engines like Railo and CF) which maybe would not appear the same in the headers. Just a wild guess. Again, asking in case you may share something that would give a clue on the FR side.
Hope that helps.
/charlie
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of Jonathan Smith
Sent: Friday, August 08, 2014 3:18 PM
To: fusion...@googlegroups.com
Subject: Re: [fusionreactor] Fusion reactor with URL Rewriting enabled
Hi,
Speaking of this: Darren, might this be something that someday you may add support for, just as the current request settings>proxy feature lets us change FR to use a different header to get the “real” ip address for a client in an environment where a load balancer or proxy would change it? Or is this need of support for rewritten URLs either a lot less frequent or a lot less standardized in terms of headers that would do the job? Or is it more complicated than this?
Asking on the list here in case the topic may interest others reading along.
/charlie
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com] On Behalf Of Jonathan Smith
Sent: Wednesday, August 13, 2014 10:45 AM
To: fusion...@googlegroups.com
Subject: Re: [fusionreactor] Fusion reactor with URL Rewriting enabled
Hi,