Postponed (maintainer needs more info)
Project:
IP to Locale
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Aug 2010 at 11:47 UTC
Updated:
28 Nov 2011 at 10:57 UTC
Jump to comment: Most recent file
Comments
Comment #1
guysaban commentedComment #2
guysaban commentedPlease find attached a patch file below for the the development version.
Comment #3
guysaban commentedAdded patch for dev. see #2 above.
PLEASE IGNORE - I DID NOT BUILD THE PATCH CORRECTLY - I'VE ATTACHED THE CORRECTED PATCH FILE FURTHER DOWN ON THIS ISSUE QUEUE.
Comment #4
guysaban commentedpatch for dev version (9-August-2010)
PLEASE IGNORE - I DID NOT BUILD THE PATCH CORRECTLY - I'VE ATTACHED THE CORRECTED PATCH FILE FURTHER DOWN ON THIS ISSUE QUEUE.
Comment #5
guysaban commentedPLEASE IGNORE - I DID NOT BUILD THE PATCH CORRECTLY - I'VE ATTACHED THE CORRECTED PATCH FILE FURTHER DOWN ON THIS ISSUE QUEUE.
Comment #6
guysaban commentedPlease find attached the correct patch file for the dev version.
Sorry for making this queue messy.
Comment #7
guysaban commentedComment #8
mrfelton commentedWhat is the problem with redirecting search engines? Why would you want to disable redirection for search engines?
Comment #9
guysaban commentedHi,
I have not researched this issue enough but my concern is how search engines will react to this feature.
Say Googlebot US visits the URL and then Googlebot UK visits the same URL but gets a redirect. How is that evaluated?
The issue with adding the option to avoid redirecting search engines is that of cloaking
At this point I am not sure whether redirecting or not redirecting search engines is a good idea.
All the best,
Guy