i update my site regularly to the latest cvs version. today i get a error. the next message flashes by :
An HTTP error 403 occured. update.php?op=do_update
. After that i get the message: there are some erors, look in the watchdog ...etc. There are no errors loged.
greetings
MM
Comments
Comment #1
Mad Maks commentedComment #2
Mad Maks commentedi am using firefox 1.5.0.1
Comment #3
Zen commentedhttp://drupal.org/node/54003
Comment #4
Mad Maks commentedi disagree. This is not a duplicate, the don't log part is but the error not.
Comment #5
Zen commentedI should have also said that I couldn't replicate the 403 issue on a fresh install. I believe that this has come up a couple of times before - please search the issue queue for more information. Perhaps fixing the watchdog issue will allow you to gauge what the issue is.
403 = access denied if you are unaware.
Sorry about that.
Cheers
-K
P.S Downgrading as this could not be duplicated on two different machines.
Comment #6
moshe weitzman commentedplease log in as user #1 and assure that you can or can't get to that update page.
Comment #7
Mad Maks commentedOf cource i was loged in as user #1. I am going to try it tomorrow again with the latest cvs version.
Comment #8
Mad Maks commentedtoday i updated to rc2 and the problem still excist in Firefox, if i use IE there is no problem.
Comment #9
Mad Maks commentedis nobody having this issue / can help me?
Comment #10
Mad Maks commentedwith the update to 4.7.3 i still have that problem
Comment #11
Mad Maks commentedturning off java is the solution.
Comment #12
magico commented@Mad Maks: could we describe better what is the problem? Can you make a clean install of 4.7.3 and then upgrade to 4.7.4 to verify if the problem does happen.
It's strange that Java is causing this problem....
Comment #13
robertgarrigos commentedI actually had the very same problem. Resolved by disabling javascript. I'm on Mac and Firefox 2.
Comment #14
robertgarrigos commentedI downloaded a fresh tarball for 4.7.3 and 4.7.4, installed and upgraded with no problem now (firefox 3). I don't think it pays to have this open bug here anymore.
Comment #15
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.