Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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.

ابحث في الدعم

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

The html tag <object> behaves differently when communicating over Wi-Fi or LTE. For WLAN, the behavior is as expected and for LTE a new session is always called

  • 1 (رد واحد)
  • 1 has this problem
  • 3 views
  • آخر ردّ كتبه Frank_VGV

more options

Hello, the html tag <object> behaves differently when communicating over Wi-Fi or LTE. For WLAN, the behavior is as expected and for LTE a new session is always called after logging in, because the transferred SessionID is not returned. Cookies are turned on in both cases. We have some websites (Example www.vw-baev.de/Registrierung) and a small portal, which we show / integrate in this website by tag <object>. We use now tag <iframe> and we succeed, but why does LTE not work? The small portal was developed with MS Visual Studio 2015 and ASPX. Many Thanks Frank

Hello, the html tag <object> behaves differently when communicating over Wi-Fi or LTE. For WLAN, the behavior is as expected and for LTE a new session is always called after logging in, because the transferred SessionID is not returned. Cookies are turned on in both cases. We have some websites (Example www.vw-baev.de/Registrierung) and a small portal, which we show / integrate in this website by tag <object>. We use now tag <iframe> and we succeed, but why does LTE not work? The small portal was developed with MS Visual Studio 2015 and ASPX. Many Thanks Frank

All Replies (1)

more options

Sorry, the tags are not displayed correctly. We switched from "<" object ">" to "<" iframe ">".