Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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 Antwort
  • 1 hat dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von Frank_VGV

Frank_VGV
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

Alle Antworten (1)

Frank_VGV
Frank_VGV Fragesteller
more options

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