Problem with redirects in coldfusion
-
How to redirect pages in cold fusion? If using ColdFusion and modrewrite, the URL will never be redirected from ModRewrite.
-
Hello! Can you give a bit more information about your set up? Coldfusion does have redirect tags you can use, but normally Coldfusion runs on IIS, so you need to set up the redirects there.
-
This post is deleted! -
I am trying to put redirects in cold fusion but when I crawl the page in moz analytics it still gives me error 500.
The redirect should point from
http://www.weddingrings.com/item.cfm?str_shortdesc=UNIQUE
to
I use the following code
<cfif query_string="" eq="" "str_shortdesc="UNIQUE""><cfheader statuscode="301" statustext="Moved Permanently"><cfheader name="Location" value="/item.cfm?str_shortdesc=UNIQUE%20CARRE%20CUT%20DIAMOND%20ETERNITY%20BAND&str_category=Diamond-Bands-and-Gold-Rings&grouping_id=9&category_id=21&int_item_id=6884"><cfabort></cfabort></cfheader></cfheader></cfif>
-
I just checked your URL and it does show a 301 redirect in my browser, in our Moz toolbar, and with our Moz crawler. Are you possibly looking at an old crawl report?
Thanks!
Jen
-
I use Crawl Diagnostic 'Analyze Issue Page by Page' and when I check this page: http://www.weddingrings.com/item.cfm?str_shortdesc=UNIQUE it returns 500 error and doesn't show redirect
-
Ok, it looks like you've set up your redirects correctly. Let me see if I can get someone who can help figure out what's going on with your crawl report.
- Jen
-
Hi!
The "Analyze Issues by Page" section actually just says that we didn't crawl that URL, not that it throws a 500 so there isn't an analysis we can provide.
http://screencast.com/t/4dY8SZBs
You can wait to see if that page is crawled during your next weekly update or run a crawl through the Crawl Test tool (in Research Tools). Crawl test will give you an analysis of up to 3k pages. There is a chance it still won't be crawled, but it is a way to get updated diagnostic data before the next scheduled weekly crawl.
There was one 500 reported in the crawl and I can confirm it's still throwing that error, but it's a completely different page. Hope this helps clear things up!