Closed Bug 419257 Opened 16 years ago Closed 15 years ago

AUS: Update XML File Malformed (200) error on the first try


(SeaMonkey :: General, defect)

Not set


(Not tracked)



(Reporter: adriank, Unassigned)


User-Agent:       Mozilla/5.0 (X11; U; Linux i686; PL; rv: Gecko/20080201 MultiZilla/ SeaMonkey/1.1.8
Build Identifier: 

It looks like on the first try to check for updates, SeaMonkey produces an "AUS: Update XML File Malformed (200)" error.
Checked on all three platforms.
A second try always work.

Reproducible: Always

Steps to Reproduce:
1. Start a SeaMonkey nightly
2. Check for updates
3. See the error
Version: unspecified → Trunk
it looks like the URL maybe points to the en-US Version, because after trying to update the Polish version I tried the same with German and French versions, and there the update was downloaded in one second. 
sorry, the comment was not intended to this bug (and has nothing to do with it)...
I read that some Firefox users see such a message when using certain personal firewalls, could that be an issue for you?
I don't think that this is the problem. Especially because I see this problem also in Linux and Mac OS X 10.5.
But something changed since Monday. On Sunday I could still reproduce this bug all the day every time I tried (at the FOSDEM room and in the hotel). But now that happens to me only from time to time... Have to investigate more...
OK, this looks like a SSL error. In the error console I see
Fehler: channel.securityInfo is null
Quelldatei: file:///mnt/mozilla/packages/
Zeile: 102

From IRC:
<Mossop> Ah, bad ssl
<Mossop> KaiRo: Most likely the request is being redirected to an insecure url

When loading manually, I get the warning box for loading an encrypted page containing unencrypted content!
Ever confirmed: true
I was just informed that the warning box could be because of XML prettyprint CSS
Setting the app.update.log.Checker pref to true at least gives some info in the error console about what it's doing
looks like a package update on aus2-community solved this
Closed: 16 years ago
Resolution: --- → FIXED
Hmm, I saw this again when testing for bug 419258 today - interestingly, it only happens on the first try to do an update, and works fine when I just try a second time. I get the same error message in the console as in comment #5
It's not always the first time, but it happens intermittently.
Here are two Checker logs from the same build, first try succeeded though it found no new updates, second try failed with the security error:

Successful log:

*** Checker: update url:
*** Checker: update url:
*** Checker: update url:
*** Checker: checkForUpdates: sending request to
*** Checker: onLoad: request completed downloading document
*** Checker: Updates available: 0

Unsuccessful log:

*** Checker: update url:
*** Checker: update url:
*** Checker: update url:
*** Checker: checkForUpdates: sending request to
*** Checker: onError: error during load
Resolution: FIXED → --- is the line that fails with the security problem (badCertHandler.js get #included in nsUpdateService.js by the preprocessor), is where it's called.

interestingly, we seem to pass the "https" test, so the channel does exist (actually the channel member of a XmlHttpRequest object), but we're unable to get the securityInfo from it.
Now after bug 451164 we maybe might get a better error message. We probably should re-try with builds that have that patch.
I cannot reproduce this error at all in recent builds. Can anyone else? Else we should mark this WFM now.
No objection to my last comment has been registered in 9 months, so marking this as WFM.
Closed: 16 years ago15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.