On Thursday 06 July 2006 11:26, Rob Wilkerson wrote:
I don't want the request to be reported as a 404. The landing page,
I *think* if you use a Handler, you can return any code you like.
--
Tom Chiverton
This email is sent for and on
If you use a CF page as the 404 page it will, by default, return a 200
status code and you will get what you want. You can set whatever
status code you want with cfheader anyway. Set the CF missing template
handler to the same page and all your requests will go through the
correct page.
On
On Wednesday 05 July 2006 22:19, Rob Wilkerson wrote:
Does that help any?
Is there some reason not to set the 404 handler in Apache to a CFM page ?
--
Tom Chiverton
This email is sent for and on behalf of Halliwells LLP.
Halliwells LLP is
I don't want the request to be reported as a 404. The landing page,
in this case is retrieving data from a database and delivering that
data as html. When delivered, the response header returns a 200 code.
On 7/6/06, Tom Chiverton [EMAIL PROTECTED] wrote:
On Wednesday 05 July 2006 22:19, Rob
I'm not exactly sure what your rules mean... I usually have a RewriteCond
that goes before a rewriteRule, so if you wanted to only redirect the cfm
pages to landingpage.cfm, you would do
RewriteCond %{REQUEST_URI} cfm$[NC]
RewriteRule ^/(.*)$/landingpage.cfm?uri=$1
Actually, I want to rewrite everything regardless of whether it's a
cfm page. The problem is that only cfm pages redirect properly. I
want '/ack/foo/blah' and '/ack/foo/blah.htm' to redirect in *addition*
to '/ack/foo/blah.cfm'. Currently, only the latter redirection works
without the PT flag.
6 matches
Mail list logo
