<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>JR-Holmes - Apache</title>
			<link>http://www.bifrost.com.au/blog/index.cfm</link>
			<description>Yet Another CF Developer</description>
			<language>en-us</language>
			<pubDate>Tue, 07 Sep 2010 17:20:06 -0700</pubDate>
			<lastBuildDate>Wed, 18 Oct 2006 22:09:00 -0700</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>james.holmes@gmail.com</managingEditor>
			<webMaster>james.holmes@gmail.com</webMaster>
			
			
			
			
			
			<item>
				<title>Changed CGI.REQUEST_URI behaviour with CF7/Apache - A Solution</title>
				<link>http://www.bifrost.com.au/blog/index.cfm/2006/10/18/Changed-CGIREQUESTURI-behaviour-with-CF7Apache--A-Solution</link>
				<description>
				
				&lt;p&gt;Those who have upgraded their Apache 2 CF servers to CF7 may have noticed that CGI.REQUEST_URI no longer contains the original request URL and query string when Apache does a 404 redirect to a CF page. For example, we just found this the hard way. In 6.1, the var would contain the original URL and the query string - it now contains the 404&amp;#39;s URL and no query string info.&lt;br /&gt;&lt;br /&gt;Well, there are other CGI vars available that do the trick: CGI.REDIRECT_URL and CGI.REDIRECT_QUERY_STRING. These contain all the original info on the request so you can get back to the way things worked before the upgrade.&lt;/p&gt;&lt;p&gt;http://httpd.apache.org/docs/2.0/custom-error.html&lt;/p&gt;
				
				</description>
						
				
				<category>ColdFusion</category>				
				
				<category>Apache</category>				
				
				<pubDate>Wed, 18 Oct 2006 22:09:00 -0700</pubDate>
				<guid>http://www.bifrost.com.au/blog/index.cfm/2006/10/18/Changed-CGIREQUESTURI-behaviour-with-CF7Apache--A-Solution</guid>
				
			</item>
			
		 	
			</channel></rss>