X-UA-Compatible

[tiagos...@gmail.com]

Hi,

I'm facing an issue where the page is not being correctly rendered in IE due to the meta tag X-UA-Compatible being set to IE=8 instead of IE=Edge. I have several web interfaces that have this issue but the newer interfaces have the tag set correctly.

The main difference between the pages that work and those that don't is the value of the field 'engine'. The pages that have the X-UA-Compatible set to IE=8 have the engine "lifou_v2" while the pages that are correctly configured have the engine "magdalena_v4".

So my questions are: Is there a way to workaround this issue? Is there any way to migrate an interface to the new engine? Will I be forced to recreate the interface to achieve this?

Thank you.

[Pankaj Kumar]

Hi,

Newly created Web Interfaces are using the engine "lifou_v3" and have the html meta data "IE=Edge" (<meta http-equiv="X-UA-Compatible" content="IE=Edge"/>), old web interface using the "magdalena_v4" have the html meta data  <meta http-equiv="X-UA-Compatible" content="IE=8" >"

If you copy the old web interface, copied web interface are using the ""lifou_v3" and have the "X-UA-Compatible" set to "Edge"

Thank you,

Pankaj Kumar

Fujitsu RunMyProcess Support

--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to the Google Groups "Fujitsu RunMyProcess Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum...@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://groups.google.com/a/runmyprocess.com/group/supportforum/.
To view this discussion on the web visit https://groups.google.com/a/runmyprocess.com/d/msgid/supportforum/4b13ec4d-ec34-4ac9-85f1-aa2e36f46d19%40runmyprocess.com.
For more options, visit https://groups.google.com/a/runmyprocess.com/d/optout.

[tiagos...@gmail.com]

Got it. Duplicating the page solves the issue but I'll have to do something about the URLs. As I'll need to prevent users that access the application through the old URL to get a 404. Is there no way to achieve this result without actually creating a new web interface?

Thanks