search

lyungn / support-tools

Automatically exported from code.google.com/p/support-tools
Apache License 2.0
0 stars 0 forks source link

Unable to undo a project move, leads to 404s. #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
So everyone can see it, this is a copy of 
https://code.google.com/p/support/issues/detail?id=33898.

What steps will reproduce the problem?
Step 1. Move a project using the "Project moved" button at 
https://code.google.com/p/mmisw/adminAdvanced
Step 2. Click on the "Publish project" button, which then appears, presumably 
to 'unmove' the forward link ("All project contents will become visible to all 
users.")
Step 3. Try to access the project

What is the expected output? What do you see instead?
Rather than restoring access to the project as it was before, all access 
attempts (whether to the root path, or to the redirect path) result in a 
redirect failure. The URL is correct 
(https://code.google.com/hosting/moved?project=mmisw in my case) but the page 
shows 404 error.  
  If you then go back and hit the Project moved button, and enter an external URL, everything looks like after step 1 above -- people get a page linking forward.  If you enter an internal project name (mmisw), we're back to the 404 error.
  While we wee in 403/404 error mode, the contents within the project were visible to direct links (at least, seemed to be for a while; but no longer).

What browser (or git/hg/svn client) are you using? On what operating
system?
Chrome on Mac 10.9.

Please provide any additional information below.

This is a copy of https://code.google.com/p/support/issues/detail?id=33898.

We do still need access to the information in this project, and would not have 
done the move if we'd realized it was irreversible and effectively removed the 
project content.

The 404 error contains the following:

404. That’s an error.

The requested URL /hosting/moved?project=mmisw was not found on this server. 
That’s all we know.

Original issue reported on code.google.com by jbgrayb...@mindspring.com on 12 Mar 2015 at 9:27

GoogleCodeExporter commented 9 years ago 
That certainly is a regression on our part. I am actually the person who wrote 
the feature, tested it, etc.

You on the project moved page you _should_ see a link to the /adminAdvanced tab 
if you are project owner. And, once you re-publish the project everything 
_should_ work as normal.

I'm very surprised at this new behavior and will look into it right away.

Original comment by chrsm...@google.com on 13 Mar 2015 at 11:37

GoogleCodeExporter commented 9 years ago 
Ok, after looking through the code I think I see the problem. When we redirect 
you to that project moved page, we return HTTP code 301 moved permanently. So 
your browser caches the redirection.

However, if you publish your project after it has moved, we will no longer 
return code 301. However, you get redirected anyways because of your browsers 
cache.

I was able to reproduce your error if I used Chrome, however if I used `curl` 
on the command line after republishing the project I got the "normal" project 
homepage.

I'll update the error code we return so that other people don't get bitten by 
this behavior. But if you wish to edit your project's homepage again, try doing 
so in an incognito window and/or in a different browser after clearing your 
cache.

Original comment by chrsm...@google.com on 13 Mar 2015 at 11:52

GoogleCodeExporter commented 9 years ago 
After publishing a project I control (game-music-emu) I still get 301s, even 
with curl (that had never before requested the project), Firefox, and incognito 
Chrome.

Since it might be a service propagation thing on Google's end I'll try again in 
a bit I suppose, but it's definitely still happening here with https.

HOWEVER, if I use http protocol things seem to work. Unfortunately Google Code 
(or the browser, not sure) seems to redirect immediately to https for both 
Firefox and Chrome, so I was only able to verify that in Konqueror and curl.

Original comment by michael....@gmail.com on 14 Mar 2015 at 12:31

GoogleCodeExporter commented 9 years ago 
I'll also note that almost all of the links (wiki, source, etc.) after landing 
in adminAdvanced seem to work just fine even in https. However 'Project Home' 
and 'Downloads' suffer redirect errors (even in Firefox using Privacy mode).

Original comment by michael....@gmail.com on 14 Mar 2015 at 12:33