frisby, to vsekakor... ampak ta ista/podobna zgodba se vlece se od 302 hijackov, pa se kar niso uredili teh zadev tako, da bi bilo kul...
ce pa malo razmislis, se pa dejansko google drzi http standardov... recimo:
301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
kar dejansko tudi naredi... domena, ki redirecta na drugo domeno, je referenca na to drugo... zato cache pokaze tisto koncno... in zato je tudi PR domene enak ciljni domeni, ker je izvorna domena pac le referenca na drugo... povsem isto kot pri spremenljivkah in referencah...
302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
V primeru 302 hijackov je tudi Google pocel tocno to...
Je pa res hudo butasto vse skupaj...