#24303 [Fbk->Opn]: Google search contains a lot of redirects back to Google
| From: | vlanard at cal dot berkeley dot edu | Date: | Thu, 21 Aug 2003 15:54:47 +0000 |
| Subject: | #24303 [Fbk->Opn]: Google search contains a lot of redirects back to Google | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-20529@lists.php.net to get a copy of this message | ||
ID: 24303
User updated by: vlanard at cal dot berkeley dot edu
Reported By: vlanard at cal dot berkeley dot edu
-Status: Feedback
+Status: Open
Bug Type: Website problem
Operating System: Windows 2000
PHP Version: 4.3.1
Assigned To: goba
New Comment:
yah, it does appear to be resolved now.
thanks.
Previous Comments:
------------------------------------------------------------------------
[2003-08-21 03:23:24] goba@php.net
The search results for control seem to be all working for me now (only
checked the first page ;) Any problem with them?
------------------------------------------------------------------------
[2003-06-24 02:13:52] goba@php.net
Commenting on the original bug submitters error report, I get the same
results, even if I reorder the site:www.php.net and the search keyword.
I don't know how you can get it differently. If you open a plain
google.com, go to advanced search, and type in control to the search
for field, and type in www.php.net to the site field, then you get to a
search result page with "control site:www.php.net" in the search field
[the same you get with PHP.net search]
Regarding URL shortucts, my question is what to header Google parses to
know that a page does not exist. We need to clean out the bogus URLs
from Google. That is we need to add code to php.net so if googlebot
revisits our site sometime, it finds that those URLs are "not found".
I guess if we return a 404 and a Location header then many browsers
will display a 404 page [eg. IE], instead of redirecting. If it is at
all possible to use 404 with a location header in HTTP...
I'll look into why those URL shortcuts are not working.
------------------------------------------------------------------------
[2003-06-23 22:04:47] philip@php.net
Btw, the following does work (using a mirror, not www):
http://uk.php.net/control-structures
------------------------------------------------------------------------
[2003-06-23 22:02:59] philip@php.net
This bug is valid. Let's be specific and use control as an example:
http://www.google.com/search?q=control+site:www.php.net&l=en
This yields the following results from Google:
1) http://www.php.net/ref.outcontrol *
2) http://www.php.net/control-structures
3) http://www.php.net/de/blog
4) http://www.php.net/elseif *
5) http://www.php.net/en/manual
6) http://www.php.net/session_cache_limiter *
The URL's with * work. The only one I see that really should work is
#2 as apparently this shortcut used to work and it should work and
present the following:
http://www.php.net/manual/en/control-structures.php
Assigning to Goba. Regarding #5, it should be manual/en, not sure what
Google is thinking there :)
------------------------------------------------------------------------
[2003-06-23 18:14:15] vlanard at cal dot berkeley dot edu
Ok, you're right that some of the Google links do work. I clicked on
several and none of them worked. A lot of them do simply resubmit a new
Google search though, perhaps because of the way you're doing the
Google redirects?
In the "control" example I cited in this bug, of the first 5 Google
results that come back, 3 of them (links #2,3,5) submit another Google
search, rather than linking into your site. I reported this bug
initially after every link I happened to click on was one of the Google
loopbacks.
Definitely not the severity of the initial bug I reported. Sorry. But
still rather funky... I've changed the bug title accordingly. Perhaps
this is just a known limitation of the redirect system, so if you want
to leave it as is, at least you now know it's happening. I won't pile
up any more comments for you. :-)
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/24303
--
Edit this bug report at http://bugs.php.net/?id=24303&edit=1