Spring Security login forwarding to blank page issue
899 views
Skip to first unread message
tim.clymer
Jun 1, 2009, 2:00:56 PM6/1/09
to Google Web Toolkit
I've done a bit of searching around the forums but haven't seen this
issue crop up (though there are plenty of blank page issues from what
I've seen). I'm having an intermittent issue where when I login to my
application (I use Spring Security as my security framework), it
forwards to my app's HTML page (my application's entry point).
Sometimes it will then load and show the application, other times it
shows just a blank page. If I refresh the blank page, my application
comes up without fail. This would lend me to believe that this is a
caching issue. Has anyone else experienced this and have any advice
on solving it?
Thanks!
issue crop up (though there are plenty of blank page issues from what
I've seen). I'm having an intermittent issue where when I login to my
application (I use Spring Security as my security framework), it
forwards to my app's HTML page (my application's entry point).
Sometimes it will then load and show the application, other times it
shows just a blank page. If I refresh the blank page, my application
comes up without fail. This would lend me to believe that this is a
caching issue. Has anyone else experienced this and have any advice
on solving it?
Thanks!
tim.clymer
Jun 1, 2009, 2:58:19 PM6/1/09
to Google Web Toolkit
Perhaps this may help in providing an answer. When I log out from my
app and go to a different browser tab and go to the URL of my app, I'd
expect to see a login screen.
Instead, it seems as though the browser is caching the page and
attempting to make calls to my services. In the response to these
services, the server (tomcat) is sending back the login page (since
I'm not logged in) as a response.
It seems like the correct approach in this case would be to make sure
the browser attempts to refresh my entry point every time so that it
will be redirected to the login. I've tried adding <meta http-
equiv="Pragma" content="no-cache"> to the top of my html file to force
this like so:
<html>
<head>
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
But to no avail. Any ideas? I'm in uncharted waters here with this
caching stuff so your help would be greatly appreciated.
Tim
app and go to a different browser tab and go to the URL of my app, I'd
expect to see a login screen.
Instead, it seems as though the browser is caching the page and
attempting to make calls to my services. In the response to these
services, the server (tomcat) is sending back the login page (since
I'm not logged in) as a response.
It seems like the correct approach in this case would be to make sure
the browser attempts to refresh my entry point every time so that it
will be redirected to the login. I've tried adding <meta http-
equiv="Pragma" content="no-cache"> to the top of my html file to force
this like so:
<html>
<head>
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
But to no avail. Any ideas? I'm in uncharted waters here with this
caching stuff so your help would be greatly appreciated.
Tim
El Mentecato Mayor
Jun 12, 2009, 10:48:47 AM6/12/09
to Google Web Toolkit
I'm experiencing the same. So far I'm blaming the problem on the
application not being production ready yet, so it is buggy and
sometimes I see some javascript errors. As these errors go away and
the application stabilizes, I'll take a look at the problem more
closely. But of course, if somebody has some clues about how to solve
the problem, I'd like to hear them... (sorry I'm of no help).
application not being production ready yet, so it is buggy and
sometimes I see some javascript errors. As these errors go away and
the application stabilizes, I'll take a look at the problem more
closely. But of course, if somebody has some clues about how to solve
the problem, I'd like to hear them... (sorry I'm of no help).
Reply all
Reply to author
Forward
0 new messages