Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

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 valiny
  • 1 manana an'ity olana ity
  • 3 views
  • Valiny farany nomen'i 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 ">".