FF3 fails to follow redirect when checking for extension updates
Sergei Zhirikov
I have moved automatic updates hosting of my extension to a new server. I
have also configured the old server to return permanent redirect (301) to
the new location for both rdf and xpi. Now if I tell Firefox 3.0b5 to check
for updates I get "An error occurred while trying to find updates for
...".From the log files on both servers I can see that FF contacts the old
server, receives redirect response, and then it does not even attempt to
follow the redirect. Both locations (the old and the new) are plain HTTP, no
SSL. The update manifest is properly signed, but that doesn't seem to be
relevant as FF doesn't even attempt to retrieve it. I'm also sure I didn't
make a mistake in the server configuration, because FF2 finds and installs
the update without any problems. Am I dealing with a bug or is it another
security restriction introduced in Firefox 3?
Didier Ernotte
| I have the same issue with my RSS extension. I have subscribed to feeds a long time ago, and never realized that these feeds has been moved to another URL because FF was able to follow the redirect. Now, FF fails at reading these feeds because it received a redirect reponse and stop there. I had to manually add code to follow the redirect. It was working fine in FF3b4 and was broken in FF3b5. Didier --- On Thu, 5/8/08, Sergei Zhirikov <sf...@yahoo.com> wrote: |
_______________________________________________ |
Dave Townsend
This seems strange as one of my own extensions has its update on a
redirect and that seemed to work fine. Can you enable
extensions.logging.enabled, then clear your error console, do an update
check for just your extension and see what appears in the console.
Dave
Sergei Zhirikov
"Dave Townsend" <dtow...@mozilla.com> wrote in message
news:GqadnZhVL-lQwLnV...@mozilla.org...
I did as you suggested (thanks). The console shows (among other non-error
messages):
Security Error: Content at http://www.old-server.net/xpi/extension.rdf may
not load data from http://www.new-server.net/files/xpi/extension.rdf.
Error: syntax error
Source file: http://www.old-server.net/xpi/extension.rdf
Line: 1, Column: 50
Source code:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
The first message explains why it doesn't try to follow redirect. The second
one shows that it try to parse the body of the redirect response as RDF.
Looks like a bug to me...
--
Sergei.
Dave Townsend
> I did as you suggested (thanks). The console shows (among other non-error
> messages):
>
> Security Error: Content at http://www.old-server.net/xpi/extension.rdf may
> not load data from http://www.new-server.net/files/xpi/extension.rdf.
>
> Error: syntax error
> Source file: http://www.old-server.net/xpi/extension.rdf
> Line: 1, Column: 50
> Source code:
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
>
> The first message explains why it doesn't try to follow redirect. The second
> one shows that it try to parse the body of the redirect response as RDF.
> Looks like a bug to me...
> --
> Sergei.
Ok I believe that this is due to an XMLHttpRequest redirect bug that has
since been fixed. If you are feeling daring then you could test this in
a current Firefox 3 nightly (should be pretty stable, we are close to
RC1 now). Otherwise if you could let me know where to find your specific
extension so I can test (by email is fine or post here) then I can
verify that myself or make sure the problem is fixed.
Dave
Mike Shaver
> If you are feeling daring then you could test this in
> a current Firefox 3 nightly (should be pretty stable, we are close to
> RC1 now).
It is significantly less daring to use FF3 nightlies right now than to
use FF3b5. :)
Mike
Sergei Zhirikov
> Ok I believe that this is due to an XMLHttpRequest redirect bug that has
> since been fixed. If you are feeling daring then you could test this in
> a current Firefox 3 nightly (should be pretty stable, we are close to
> RC1 now). Otherwise if you could let me know where to find your specific
> extension so I can test (by email is fine or post here) then I can
> verify that myself or make sure the problem is fixed.
>
> Dave
>
I've tried the latest nightly build. Indeed, the problem has been fixed. The
update works fine. Thanks.
Sergei.
Dave Townsend
Excellent news, thanks for letting us know.
Dave