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?
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 <sfzhi@yahoo.com> wrote:
From: Sergei Zhirikov <sfzhi@yahoo.com> Subject: FF3 fails to follow redirect when checking for extension updates To: dev-extensions@lists.mozilla.org Date: Thursday, May 8, 2008, 6:03 PM
Hi all,
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?
_______________________________________________ dev-extensions mailing
list dev-extensions@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-extensions
> 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?
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.
> > 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?
> 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.
I did as you suggested (thanks). The console shows (among other non-error messages):
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.
> 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.
On Fri, May 9, 2008 at 3:08 PM, Dave Townsend <dtowns...@mozilla.com> wrote: > 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. :)
> 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 Zhirikov wrote: > "Dave Townsend"<dtowns...@mozilla.com> wrote in message > news:a72dnX7Xv8HUVrnVnZ2dnUVZ_gGdnZ2d@mozilla.org... >> 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.
|
