Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Browser version changes when deployed


This question is answered. Helpful answers available: 0. Correct answers available: 1.


Permlink Replies: 13 - Last Post: Jan 12, 2015 1:52 AM Last Post By: Justin Philbrow
Justin Philbrow

Posts: 40
Registered: 6/14/10
Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 4, 2015 11:43 AM
Hi,

I have Delphi XE6 and IntraWeb 14.0.32.

While developing an intraweb application on my local PC (Windows 7 32bit) my application runs and looks fine on IE and other browsers (Firefox, Chrome and Opera), But when I deploy my stand alone IW app to our server and connect and load the pages from my PC using the same IE browser much of the formatting is changed and I notice that my browser is not being recognized by my IW app.

IE version is IE 10.

When I run on my own PC when using IE, the version is seen seen as: BrowserName: Microsoft Internet Explorer (10) MV: 10 MINV: 8
When I run the IW on our server and I connect with same IE browser, it is "seen" as: BrowserName: Microsoft Internet Explorer (8) MV: 8 MINV: 8

This is because in the ServerController Basebrowsercheck I have used the suggested code which includes:

[...]
// if is IE, but older or unsupported version
else if (rBrowser is TInternetExplorer) and (not rBrowser.IsSupported) then begin
rBrowser.Free;
// we will create it as the minimum supported version. Please note that we are using TInternetExplorer.MIN_VERSION class property
rBrowser := TInternetExplorer.Create(TInternetExplorer.MIN_VERSION);
end;

My question is: why does the IW standalone server "see" my IE browser differently depending where it is located (i.e. when run on my PC vs on our server)?

Needless to say this causes a headache in development/deployment.
Chad Hower

Posts: 613
Registered: 3/2/07
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 4, 2015 12:52 PM   in response to: Justin Philbrow in response to: Justin Philbrow
Can you check the raw browser string and post it?

Possibly there could be a proxy in the middle which is altering the
browser string.

On 1/4/2015 3:43 PM, Justin Philobrow wrote:
Hi,

I have Delphi XE6 and IntraWeb 14.0.32.

While developing an intraweb application on my local PC (Windows 7 32bit) my application runs and looks fine on IE and other browsers (Firefox, Chrome and Opera), But when I deploy my stand alone IW app to our server and connect and load the pages from my PC using the same IE browser much of the formatting is changed and I notice that my browser is not being recognized by my IW app.

IE version is IE 10.

When I run on my own PC when using IE, the version is seen seen as: BrowserName: Microsoft Internet Explorer (10) MV: 10 MINV: 8
When I run the IW on our server and I connect with same IE browser, it is "seen" as: BrowserName: Microsoft Internet Explorer (8) MV: 8 MINV: 8

This is because in the ServerController Basebrowsercheck I have used the suggested code which includes:

[...]
// if is IE, but older or unsupported version
else if (rBrowser is TInternetExplorer) and (not rBrowser.IsSupported) then begin
rBrowser.Free;
// we will create it as the minimum supported version. Please note that we are using TInternetExplorer.MIN_VERSION class property
rBrowser := TInternetExplorer.Create(TInternetExplorer.MIN_VERSION);
end;

My question is: why does the IW standalone server "see" my IE browser differently depending where it is located (i.e. when run on my PC vs on our server)?

Needless to say this causes a headache in development/deployment.

--
"Programming is an art form that fights back"
IntraWeb IRC and Web Chat:
http://www.atozed.com/intraweb/Support/IRC.aspx

Justin Philbrow

Posts: 40
Registered: 6/14/10
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 5, 2015 8:07 AM   in response to: Chad Hower in response to: Chad Hower
Hi Chad,

UserAgent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1;Trident/6.0)

Is that what you mean?

I notice that on the server where the stand alone IW app is running, IE is installed and it is version 8. Could it be that the installed IE version on the server where the stand alone is running affects what the IW app sends out?

Otherwise I changed the Compatibility view as pr post below and it works, but I want to, 1 understand the cause of this, and 2, I dont want to have to ask the users to change any settings in their browsers.

Chad Hower wrote:
Can you check the raw browser string and post it?

Possibly there could be a proxy in the middle which is altering the
browser string.

On 1/4/2015 3:43 PM, Justin Philobrow wrote:
Hi,

I have Delphi XE6 and IntraWeb 14.0.32.

While developing an intraweb application on my local PC (Windows 7 32bit) my application runs and looks fine on IE and other browsers (Firefox, Chrome and Opera), But when I deploy my stand alone IW app to our server and connect and load the pages from my PC using the same IE browser much of the formatting is changed and I notice that my browser is not being recognized by my IW app.

IE version is IE 10.

When I run on my own PC when using IE, the version is seen seen as: BrowserName: Microsoft Internet Explorer (10) MV: 10 MINV: 8
When I run the IW on our server and I connect with same IE browser, it is "seen" as: BrowserName: Microsoft Internet Explorer (8) MV: 8 MINV: 8

This is because in the ServerController Basebrowsercheck I have used the suggested code which includes:

[...]
// if is IE, but older or unsupported version
else if (rBrowser is TInternetExplorer) and (not rBrowser.IsSupported) then begin
rBrowser.Free;
// we will create it as the minimum supported version. Please note that we are using TInternetExplorer.MIN_VERSION class property
rBrowser := TInternetExplorer.Create(TInternetExplorer.MIN_VERSION);
end;

My question is: why does the IW standalone server "see" my IE browser differently depending where it is located (i.e. when run on my PC vs on our server)?

Needless to say this causes a headache in development/deployment.

--
"Programming is an art form that fights back"
IntraWeb IRC and Web Chat:
http://www.atozed.com/intraweb/Support/IRC.aspx

Chad Hower

Posts: 613
Registered: 3/2/07
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 6, 2015 8:15 AM   in response to: Justin Philbrow in response to: Justin Philbrow
On 1/5/2015 12:07 PM, Justin Philobrow wrote:
UserAgent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT
6.1;Trident/6.0)

Is that what you mean?

Yes, but I meant from both. ie locally and remote so we can compare the
differences.

I notice that on the server where the stand alone IW app is running,
IE is installed and it is version 8. Could it be that the installed
IE version on the server where the stand alone is running affects
what the IW app sends out?

Not likely.

Otherwise I changed the Compatibility view as pr post below and it
works, but I want to, 1 understand the cause of this, and 2, I dont
want to have to ask the users to change any settings in their
browsers.

This was my next guess as well that it might be bypassing it when
locally. IE continues to be a huge headache and this compatibility mode
seems to make a far bigger problem than the one it was designed to fix.

Compatibility mode has a lot of issues. I know Alexandre dug into this
quite a bit and I'm sure he has an answer but due to some unforeseen
circumstances will be at least a week late returning from holiday.
Hopefully he will be able to chime in next week if you can wait a few
more days.

--
"Programming is an art form that fights back"
IntraWeb IRC and Web Chat:
http://www.atozed.com/intraweb/Support/IRC.aspx
Justin Philbrow

Posts: 40
Registered: 6/14/10
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 7, 2015 1:17 AM   in response to: Chad Hower in response to: Chad Hower
Many thanks Chad,

Locally run I get this: UserAgent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0) - i.e. the same.

brgds
Justin

Chad Hower wrote:
On 1/5/2015 12:07 PM, Justin Philobrow wrote:
UserAgent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT
6.1;Trident/6.0)

Is that what you mean?

Yes, but I meant from both. ie locally and remote so we can compare the
differences.

I notice that on the server where the stand alone IW app is running,
IE is installed and it is version 8. Could it be that the installed
IE version on the server where the stand alone is running affects
what the IW app sends out?

Not likely.

Otherwise I changed the Compatibility view as pr post below and it
works, but I want to, 1 understand the cause of this, and 2, I dont
want to have to ask the users to change any settings in their
browsers.

This was my next guess as well that it might be bypassing it when
locally. IE continues to be a huge headache and this compatibility mode
seems to make a far bigger problem than the one it was designed to fix.

Compatibility mode has a lot of issues. I know Alexandre dug into this
quite a bit and I'm sure he has an answer but due to some unforeseen
circumstances will be at least a week late returning from holiday.
Hopefully he will be able to chime in next week if you can wait a few
more days.

--
"Programming is an art form that fights back"
IntraWeb IRC and Web Chat:
http://www.atozed.com/intraweb/Support/IRC.aspx
Alexandre Machado

Posts: 1,754
Registered: 8/10/13
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 8, 2015 6:36 AM   in response to: Justin Philbrow in response to: Justin Philbrow
Please check Cees Glas answer. He is correct. IE has these stupid settings.... It is most likely to be the cause of the problem.
Justin Philbrow

Posts: 40
Registered: 6/14/10
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 8, 2015 6:49 AM   in response to: Alexandre Machado in response to: Alexandre Machado
Hi Alexandre,

I checked and, as I mention above, it is the case. But I cant deploy an application and expect my users to disable this in their browsers.
Also I dont understand why it makes a difference if the stand alone app is running on my machine (compatibility is not an issue) or on a server (compatibility is an issue). I am using the same app and the same browser, yet getting compatibility issue...?

brgds
Justin

Alexandre Machado wrote:
Please check Cees Glas answer. He is correct. IE has these stupid settings.... It is most likely to be the cause of the problem.
Alexandre Machado

Posts: 1,754
Registered: 8/10/13
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 8, 2015 7:25 AM   in response to: Justin Philbrow in response to: Justin Philbrow
Justin Philobrow wrote:
Hi Alexandre,

I checked and, as I mention above, it is the case. But I cant deploy an application and expect my users to disable this in their browsers.
Also I dont understand why it makes a difference if the stand alone app is running on my machine (compatibility is not an issue) or on a server (compatibility is an issue). I am using the same app and the same browser, yet getting compatibility issue...?

brgds
Justin

But this is how IE works. This is one of the zillions of stupid things that people at Microsoft does everyday and we have to deal with it!

This setting says to IE:

If your site is a local site, render it as an old IE does. If not, render it as it is the current version. IntraWeb has no control over it,

Your customers will run it as a external (internet) or internal (intranet) application?
Justin Philbrow

Posts: 40
Registered: 6/14/10
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 8, 2015 7:48 AM   in response to: Alexandre Machado in response to: Alexandre Machado
Understood :-(

They will run it as an internal intranet application.

brgds
Justin

Alexandre Machado wrote:
Justin Philobrow wrote:
Hi Alexandre,

I checked and, as I mention above, it is the case. But I cant deploy an application and expect my users to disable this in their browsers.
Also I dont understand why it makes a difference if the stand alone app is running on my machine (compatibility is not an issue) or on a server (compatibility is an issue). I am using the same app and the same browser, yet getting compatibility issue...?

brgds
Justin

But this is how IE works. This is one of the zillions of stupid things that people at Microsoft does everyday and we have to deal with it!

This setting says to IE:

If your site is a local site, render it as an old IE does. If not, render it as it is the current version. IntraWeb has no control over it,

Your customers will run it as a external (internet) or internal (intranet) application?
Alexandre Machado

Posts: 1,754
Registered: 8/10/13
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 8, 2015 8:43 AM   in response to: Justin Philbrow in response to: Justin Philbrow
Justin Philobrow wrote:
Understood :-(

They will run it as an internal intranet application.

brgds
Justin

And your application renders correctly when it is using the compatibility mode or not?
Cees Glas

Posts: 4
Registered: 10/10/01
Re: Browser version changes when deployed
Helpful
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 8, 2015 11:26 PM   in response to: Justin Philbrow in response to: Justin Philbrow
In our organisation it's possible for the IT department to change this setting through the (network) policy. Maybe that's also possible in your network?

Justin Philobrow wrote:
Understood :-(

They will run it as an internal intranet application.

brgds
Justin

Alexandre Machado wrote:
Justin Philobrow wrote:
Hi Alexandre,

I checked and, as I mention above, it is the case. But I cant deploy an application and expect my users to disable this in their browsers.
Also I dont understand why it makes a difference if the stand alone app is running on my machine (compatibility is not an issue) or on a server (compatibility is an issue). I am using the same app and the same browser, yet getting compatibility issue...?

brgds
Justin

But this is how IE works. This is one of the zillions of stupid things that people at Microsoft does everyday and we have to deal with it!

This setting says to IE:

If your site is a local site, render it as an old IE does. If not, render it as it is the current version. IntraWeb has no control over it,

Your customers will run it as a external (internet) or internal (intranet) application?
Alexandre Machado

Posts: 1,754
Registered: 8/10/13
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 9, 2015 2:17 AM   in response to: Justin Philbrow in response to: Justin Philbrow
The only real effective way to force IE to render it properly is sending the X-UA-Compatible value as a header field in the http response, because it is ignored when in HTML as a tag, under some circumstances.

We are changing our implementation and we will send it as a header field. This should be available in the next version. We expect to release it next week.

Best regards
Justin Philbrow

Posts: 40
Registered: 6/14/10
Re: Browser version changes when deployed  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 12, 2015 1:52 AM   in response to: Alexandre Machado in response to: Alexandre Machado
OK, thanks.

Alexandre Machado wrote:
The only real effective way to force IE to render it properly is sending the X-UA-Compatible value as a header field in the http response, because it is ignored when in HTML as a tag, under some circumstances.

We are changing our implementation and we will send it as a header field. This should be available in the next version. We expect to release it next week.

Best regards
Cees Glas

Posts: 4
Registered: 10/10/01
Re: Browser version changes when deployed
Helpful
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 5, 2015 7:18 AM   in response to: Justin Philbrow in response to: Justin Philbrow
This might be caused by the compatibility view settings of your Internet Explorer. Press ALT+T in Internet Explorer, select Compatibility View Settings from the menu. If the setting 'Display Intranet sites in compatibility view' is checked, you could try unchecking it to see if the pages are rendered correctly.

Justin Philobrow wrote:
Hi,

I have Delphi XE6 and IntraWeb 14.0.32.

While developing an intraweb application on my local PC (Windows 7 32bit) my application runs and looks fine on IE and other browsers (Firefox, Chrome and Opera), But when I deploy my stand alone IW app to our server and connect and load the pages from my PC using the same IE browser much of the formatting is changed and I notice that my browser is not being recognized by my IW app.

IE version is IE 10.

When I run on my own PC when using IE, the version is seen seen as: BrowserName: Microsoft Internet Explorer (10) MV: 10 MINV: 8
When I run the IW on our server and I connect with same IE browser, it is "seen" as: BrowserName: Microsoft Internet Explorer (8) MV: 8 MINV: 8

This is because in the ServerController Basebrowsercheck I have used the suggested code which includes:

[...]
// if is IE, but older or unsupported version
else if (rBrowser is TInternetExplorer) and (not rBrowser.IsSupported) then begin
rBrowser.Free;
// we will create it as the minimum supported version. Please note that we are using TInternetExplorer.MIN_VERSION class property
rBrowser := TInternetExplorer.Create(TInternetExplorer.MIN_VERSION);
end;

My question is: why does the IW standalone server "see" my IE browser differently depending where it is located (i.e. when run on my PC vs on our server)?

Needless to say this causes a headache in development/deployment.
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02