|
|
Rank: Member
Groups: Member
Joined: 9/16/2015
Posts: 18
|
Hi,
setting CustomUserAgent
- req header : Ok
- navigator.userAgent, navigator.appVersion does not changed.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
This is a limitation of this feature. Currently CustomUserAgent is implemented as a overriding HTTP header, so it only affects server side. Thus it is not possible for you to replace navigator.userAgent. Generally it is not a good idea for you to replace navigator.userAgent since so many web page parses this string and acts differently depends on what they see in this string.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/16/2015
Posts: 18
|
Hi,
wb.CustomUserAgent = "Mozilla/5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Mobile Safari/537.36";
1. EO 2015~2018
navigator.appVersion: "5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Mobile Safari/537.36"
navigator.userAgent: "Mozilla/5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Mobile Safari/537.36"
2. EO 2019
navigator.appVersion: "5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36"
navigator.userAgent: "Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36"
feature changed?
Thanks.
|
|
Rank: Advanced Member
Groups: Member
Joined: 9/20/2016
Posts: 73
|
ClearSoft, thanks for paying attention!
It's a security hole:(
Update: you can use "--user-agent" commandline flag to fix it, but it is not comfortable in some cases...
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Yes. This indeed is a problem. We should be able to address it in our next build. We will reply here again as soon as the new build is available.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
This is just to let you know that we have posted a new build that should resolve this issue. Please see your private message for the download location.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/16/2015
Posts: 18
|
Hi,
Thank you for the new build.
It works!
Thanks :)
|
|
Rank: Member
Groups: Member
Joined: 9/16/2015
Posts: 18
|
Hi,
Another error was found in the test build.
* EnableEOWP = true; (put eowp.exe in the app dir)
Multiple executions of app.exe will result in the following error:
"Can not find or automatically create eowp.exe. Please place this file in the same directory as EO.Base.dll and make sure they are the same version. This file is needed if your application does not have sufficient permission to read Windows system directory, or you have EO.Base.Runtime.EnableEOWP set to true. .'C:\Users\...\AppData\Local\Temp\eowp.19.0...."
I will wait for the official version.
Thank you.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
This does not have anything to do with the change in the new build about CustomUserAgent. You can run into this error when the application tries to automatically create eowp.exe and you have multiple instance of the application trying to start at the same time (we do have additional code try to avoid such conflict but it's not guaranteed).
The easiest way to avoid this problem is to make sure you have eowp.exe in your application's directory or bin directory (check AppDomain.CurrentDomain.BaseDirectory or "bin" directory under that directory). If you have the correct eowp.exe in those two directory, then your application will not try to automatically create eowp.exe in your temp directory and run into race conditions.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/16/2015
Posts: 18
|
Hi,
I already know this.
It is just an error in the test build. 19.0.56 and EO 2015 ~ 2018 will work normally.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
I am not sure what else to tell you. What we were trying to tell you in our previous post is this has nothing to do with the test build. Nothing in the test build has changed regarding eowp.exe and the error message clear indicates that it did NOT find eowp.exe in your app directory. So that's where you need to look. If you do not believe what we tell you and still believe this has to do with the test build, you are welcome to wait for the public build.
|
|
Rank: Member
Groups: Member
Joined: 9/16/2015
Posts: 18
|
TabbedBrowser_CS sample
App.xaml.cs
.....
> EO.Base.Runtime.EnableEOWP = true;
EO.Base.Runtime.StartDebugMonitor("test");
.....
1. build and copy to "C:\Program Files (x86)\Essential Objects\EO.Total 2019\TabbedBrowser.exe" (install dir)
2. run twice
There is obviously an error in the test build. I just hope there is no problem with the public build.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
There must be something different on your system. We tested exactly that here and it worked fine. :((
|
|
Rank: Member
Groups: Member
Joined: 9/16/2015
Posts: 18
|
Hi,
[EO 19.0.69] CustomUserAgent, EnableEOWP
it worked fine!
Thanks :)
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Great!
|
|