i just made a simple solution with a button doing this:
application.showURL('http://www.nu.nl', "_self");
application.exit();
and it works fine for me.
logout to expire page on webclient
36 posts
• Page 3 of 3 • 1, 2, 3
Re: logout to expire page on webclient
by jcompagner » Wed Nov 10, 2010 6:14 pm
Johan Compagner
Servoy
Servoy
-
jcompagner - Posts: 8833
- Joined: Tue May 27, 2003 7:26 pm
- Location: The Internet
Re: logout to expire page on webclient
by bobpee » Wed Nov 10, 2010 6:31 pm
i just made a simple solution with a button doing this:
application.showURL('http://www.nu.nl', "_self");
application.exit();
and it works fine for me.
That's right, that's what we have been doing all the time too and it had always worked fine for us,alas, until recently.
By the way, Johan, have you run your sample solution on a Window Server 2003? This is the OS that we've have been doing our staging/testing on and it appears to be giving unpredictable results, at least lately.
We want to be sure that it is nothing like a "Win Server 2003" bug. We test code locally on our Win XPs and Vistas and Win 7 and we get positive results, But on Window Server 2003 with same code, this behavior is showing up.
Bob Prah,
[Servoy 5.2.4 - build 1006]
[Servoy 5.2.4 - build 1006]
-
bobpee - Posts: 81
- Joined: Tue Mar 04, 2008 1:05 pm
Re: logout to expire page on webclient
by jcompagner » Wed Nov 10, 2010 6:51 pm
Are we talking here about the server or a browser (so a client) on Win2003?
it really shouldnt matter if win2003 is the server and the browser is XP or Win7.. compared to another server machine and the browsers are XP or Win7
The response that is generated by a serer should be exactly the same.
So maybe it is the location that is different? (where the server is?)
it really shouldnt matter if win2003 is the server and the browser is XP or Win7.. compared to another server machine and the browsers are XP or Win7
The response that is generated by a serer should be exactly the same.
So maybe it is the location that is different? (where the server is?)
Johan Compagner
Servoy
Servoy
-
jcompagner - Posts: 8833
- Joined: Tue May 27, 2003 7:26 pm
- Location: The Internet
Re: logout to expire page on webclient
by bobpee » Wed Nov 10, 2010 9:12 pm
The response that is generated by a serer should be exactly the same.
So maybe it is the location that is different? (where the server is?)
I think I am missing this one - can you elaborate a bit more? - you mean the location of our test server? The one in question is on site,that is, where we do our dev work.
I am not concluding, but are you ruling-out that the issue may also not be a-larry-ellison-effect on Win2003Ser? We'aint able to reproduce this behavior on Win Vista/Xp/7 .
Bob Prah,
[Servoy 5.2.4 - build 1006]
[Servoy 5.2.4 - build 1006]
-
bobpee - Posts: 81
- Joined: Tue Mar 04, 2008 1:05 pm
Re: logout to expire page on webclient
by jcompagner » Thu Nov 11, 2010 10:59 am
win2003 is only the server right? Its not the client (where the browser runs in?)
so that same solution running on Vista/Xp/7 is that on the same network as the win2003 server and the client where you test that redirect on is on the same client (so that is the same browser connecting now to a vista server compared to the win2003 server)??
so that same solution running on Vista/Xp/7 is that on the same network as the win2003 server and the client where you test that redirect on is on the same client (so that is the same browser connecting now to a vista server compared to the win2003 server)??
Johan Compagner
Servoy
Servoy
-
jcompagner - Posts: 8833
- Joined: Tue May 27, 2003 7:26 pm
- Location: The Internet
Re: logout to expire page on webclient
by bobpee » Thu Nov 11, 2010 3:53 pm
Hi Johan,
You know what? There's good news.
Now this is what is happening, we managed to get a workaround for our logout issue:
1. To get our solution centralize a webclient, we have had to embed the call to start Servoy webclient in an <iframe> in a simple html file like :
2. The html in (1) has worked all the time for us in the past. A logout from our solution in webclient has always redirected to a predefined URL - and we haven't changed any part of this.
However, recently, the above html with the <iframe > is unable to handle a
showURL followed by an application.exit(), which is how we get out of a webclient on a logout.
Using the method in (1) this time around throws an "error calling server" in webclient and the showURL doesn't perform,keeping the user still
in the webclient's page. This also throws the error stack :
on the server.
3. If we are to start our webclient directly such as:
http://www.mydomain.nl/servoy-webclient ... ysolution/
our we users are able to logout of our webclient successfully, showURL does what is expected by directing an URL such as http://www.nu.nl . Additionally there is no exception whatsoever thrown by a call of the method application.exit() after a showURL.
4. We have decided to use the approach described in (3) for the time being.
Hope nobody got angry
10q
You know what? There's good news.
Now this is what is happening, we managed to get a workaround for our logout issue:
1. To get our solution centralize a webclient, we have had to embed the call to start Servoy webclient in an <iframe> in a simple html file like :
- Code: Select all
<html>
<head>
<title>MySolution</title>
</head>
<body>
<center>
<iframe scrolling="no" height="100%" width="100%" frameborder="0" src="http://www.mydomain.nl/servoy-webclient/solutions/solution/mysolution/">Sorry, MySolution does not support your browser</iframe>
</center>
</body>
</html>
2. The html in (1) has worked all the time for us in the past. A logout from our solution in webclient has always redirected to a predefined URL - and we haven't changed any part of this.
However, recently, the above html with the <iframe > is unable to handle a
showURL followed by an application.exit(), which is how we get out of a webclient on a logout.
Using the method in (1) this time around throws an "error calling server" in webclient and the showURL doesn't perform,keeping the user still
in the webclient's page. This also throws the error stack :
2010-11-09 11:43 http-8088-4 INFO com.servoy.j2db.util.Debug shutDown
2010-11-09 11:43 http-8088-4 WARN com.servoy.j2db.util.Debug Solution already closed, ignoring exception
...
.
.
Caused by: com.servoy.j2db.ExitScriptException: Application exit
at com.servoy.j2db.scripting.JSApplication.js_exit(JSApplication.java:1222)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
...
...
on the server.
3. If we are to start our webclient directly such as:
http://www.mydomain.nl/servoy-webclient ... ysolution/
our we users are able to logout of our webclient successfully, showURL does what is expected by directing an URL such as http://www.nu.nl . Additionally there is no exception whatsoever thrown by a call of the method application.exit() after a showURL.
4. We have decided to use the approach described in (3) for the time being.
Hope nobody got angry
10q
Bob Prah,
[Servoy 5.2.4 - build 1006]
[Servoy 5.2.4 - build 1006]
-
bobpee - Posts: 81
- Joined: Tue Mar 04, 2008 1:05 pm
36 posts
• Page 3 of 3 • 1, 2, 3
Who is online
Users browsing this forum: No registered users and 12 guests