This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Cari Bantuan

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.

Pelajari Lebih Lanjut

Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.

Google link traslate stopped working

  • 2 balas
  • 1 memiliki masalah ini
  • 7 kunjungan
  • Balasan terakhir oleh doco

doco
doco
more options

when I try to translate a link, google creates an interactive page with iframe and mixed content (http and https)

Firefox console reports this error: "Load denied by X-Frame-Options: http://translate.google.com/translate?.... does not permit cross-origin framing" and the response header contains "X-Frame-Options: SAMEORIGIN"

The url in the address bar is "https://translate.google.it/translate?..." I solve by changing it to "http://translate.google.it/translate?..."

This is a bug?

when I try to translate a link, google creates an interactive page with iframe and mixed content (http and https) Firefox console reports this error: "Load denied by X-Frame-Options: http://translate.google.com/translate?.... does not permit cross-origin framing" and the response header contains "X-Frame-Options: SAMEORIGIN" The url in the address bar is "https://translate.google.it/translate?..." I solve by changing it to "http://translate.google.it/translate?..." This is a bug?

Semua Balasan (2)

guigs
guigs
more options

Hi doco,

There is an add on for that, its called Quick Translator 1.0. It translates in the page for convenience.

If the http to https fixes the issue, what is the preference in about:config for https sites? It is called network.websocket.allowInsecureFromHTTPS

Looking forward to your reply.

doco
doco Pemilik pertanyaan
more options

Hi guigs2,

network.websocket.allowInsecureFromHTTPS is set to default value (false), changing it to true does not fix the issue

I read RFC7034 "HTTP Header Field X-Frame-Options", it talks about the concept of the "same origin" and refer to rfc6454 for details: '...Any data beyond the domain address (i.e., any data after the "/" separator) is to be ignored. The algorithm to compare origins from [RFC6454] SHOULD be used to verify that a referring page is of the same origin as the content...'

RFC6454 explains that: '...Roughly speaking, two URIs are part of the same origin (i.e., represent the same principal) if they have the same scheme, host, and port...'

The iframe src is relative (that is https) but its GET is redirected (with http code 302) to an identical url http

Then, I think that Firefox is simply "strict" in the matter of same origin. Http and Https differ in schema (and port) then are not the "same origin".

Thanks for reply