Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Unable to open PDF attachments from Agile with the Firefox browser

  • 1 freagra
  • 1 leis an bhfadhb seo
  • 91 views
  • Freagra is déanaí ó kobe

Chris Cannata
Chris Cannata
more options

About a week ago, I noticed that I was suddenly unable to open PDF attachments in Agile by clicking on them. Previously, I could open the attachments by clicking on them. The browser would pop up a download warning dialog, and after I acknowledged the warning statement, it would download the attachment to a download folder where I could open it with Acrobat reader.

Now, I get the warning pop-up but it does not download the attachment after I acknowledge the warning. I do not get any errors.

This seems to only affect the Firefox browser, and I now have this problem on my laptop when logged in as myself (Win7), and in the hardware lab computers when logged in as hwlab (WinXP). In both places, I can still download PDF attachments from Chrome, so it seems like it might be a browser problem but I don't know what.

I have reset all cookies and history, and even went so far as to uninstall and reinstall the browser, with no improvement.

The next step I tried was to downgrade to older FireFox (version 22) and it does work correctly. So this appears to be an incompatibility between Agile and the newest version of Firefox.

I think the reason this happens is that Firefox 23 introduced a mixed-content feature (see https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23 ).

Is there a fix for this?

About a week ago, I noticed that I was suddenly unable to open PDF attachments in Agile by clicking on them. Previously, I could open the attachments by clicking on them. The browser would pop up a download warning dialog, and after I acknowledged the warning statement, it would download the attachment to a download folder where I could open it with Acrobat reader. Now, I get the warning pop-up but it does not download the attachment after I acknowledge the warning. I do not get any errors. This seems to only affect the Firefox browser, and I now have this problem on my laptop when logged in as myself (Win7), and in the hardware lab computers when logged in as hwlab (WinXP). In both places, I can still download PDF attachments from Chrome, so it seems like it might be a browser problem but I don't know what. I have reset all cookies and history, and even went so far as to uninstall and reinstall the browser, with no improvement. The next step I tried was to downgrade to older FireFox (version 22) and it does work correctly. So this appears to be an incompatibility between Agile and the newest version of Firefox. I think the reason this happens is that Firefox 23 introduced a mixed-content feature (see https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23 ). Is there a fix for this?

All Replies (1)

kobe
kobe
more options

Hello,

Starting in Firefox 23, if a secure page includes certain types of insecure content, Firefox blocks the insecure content and a shield icon will appear in the address bar. See this article for more information about the new mixed content blocker: Mixed content blocking in Firefox

To temporarily allow the mixed content to be displayed:

  • Click the shield icon Mixed Content Shield in the address bar and choose Disable Protection on This Page from the dropdown menu.

Fx23MixedContentBlocker

To allow insecure content to be displayed in all secure pages, enter about:config in the address bar and double-click on this preference, to toggle it from true to false:

security.mixed_content.block_active_content

You can also use this add-on instead, to toggle the preference:

You may want to do this only for the current session, then reset the preference back to "true" and check back with the site to see whether it's been fixed, since this is a global setting that exposes you on all sites, not just the one you care about.

Let us know if this helps!