Fungování této stránky je z důvodu údržby dočasně omezeno. Pokud žádný článek nápovědy nevyřeší váš problém a potřebujete se zeptat na další řešení, napište nám na Twitter @FirefoxSupport nebo Reddit /r/firefox.

Avatar for Username

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Toto vlákno bylo archivováno. Pokud potřebujete pomoci, založte prosím nový dotaz.

Google link traslate stopped working

  • 2 odpovědi
  • 1 má tento problém
  • 7 zobrazení
  • Poslední odpověď od 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?

Všechny odpovědi (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 Autor dotazu
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