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

This thread was archived. Please ask a new question if you need help.

Firefox changes scheme (HTTPS for HTTP) when using relative paths.

  • No replies
  • 0 have this problem
  • 12 views
juan.velasquez
juan.velasquez
more options

We are experiencing an issue with our web application... we do form action and iframe src changes dynamically with Javascript to redirect the user to different pages within our app.

We do so using relative paths, however although the website is loaded in HTTPS, "sometimes" when we do these changes in src, or action and then submit... Firefox seems to be changing the scheme protocol, from https to http, thus we are getting mixed content blocking.

But we are not really using mixed content... our calls do not include absolute URLs, so there should not be any mixed content issue.

This is an example of the change within the source of an iframe:

document.getElementById('piframe'+id).innerHTML='<iframe src="../fondo.html" id="ttab'+id+'" name="ttab'+id+'" width="100%" scrolling="auto" height="' + espacio_iframe+'" '+ scroll + ' frameborder="0"></iframe>'

And this is an example of what we do changing the action:

document.form1.action = '../'+url; document.form1.submit();

Both actions use relative paths... and both actions throw mixed content block.

This happens only with Firefox... what might be the cause?

Thanks for your help?

We are experiencing an issue with our web application... we do form action and iframe src changes dynamically with Javascript to redirect the user to different pages within our app. We do so using relative paths, however although the website is loaded in HTTPS, "sometimes" when we do these changes in src, or action and then submit... Firefox seems to be changing the scheme protocol, from https to http, thus we are getting mixed content blocking. But we are not really using mixed content... our calls do not include absolute URLs, so there should not be any mixed content issue. This is an example of the change within the source of an iframe: document.getElementById('piframe'+id).innerHTML='<iframe src="../fondo.html" id="ttab'+id+'" name="ttab'+id+'" width="100%" scrolling="auto" height="' + espacio_iframe+'" '+ scroll + ' frameborder="0"></iframe>' And this is an example of what we do changing the action: document.form1.action = '../'+url; document.form1.submit(); Both actions use relative paths... and both actions throw mixed content block. This happens only with Firefox... what might be the cause? Thanks for your help?