We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox Can’t Open This Page

more options

When I try to open a what may be a link in a page, which should bring up a PDF file, I think, I get the following:


Firefox Can’t Open This Page

To protect your security, api.medicare.gov will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.

Learn more…

When I click on the Open Site in new Window button I get a new window with the following:


message "Unauthorized" context {} code null

When I try to open a what may be a link in a page, which should bring up a PDF file, I think, I get the following: Firefox Can’t Open This Page To protect your security, api.medicare.gov will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window. Learn more… When I click on the Open Site in new Window button I get a new window with the following: message "Unauthorized" context {} code null

所有回复 (1)

more options

Hmm, Unauthorized makes me think that your sign-in on the main page wasn't shared with the related server. Firefox recently rolled out "Total Cookie Protection." This feature limits how sites can use "third party" or "cross-site" cookies, meaning cookies from different websites than the one you see in the address bar (in this case, "api" is a different server than, say, "www").

You can make exceptions to this feature when needed by disabling Tracking Protection on the site -- repeat as needed for each server that you visit as part of the process of using this service. More info in the following articles:

Any difference?