"worked fine on ssl as it bypassed the firewall"

Then one possiblity is to redirect to HTTPS imediatelly when someone
accesses the page through HTTP.

But the GWT loading check should be implemented nonetheless.


On Aug 4, 3:33 pm, Joe Cole <profilercorporat...@gmail.com> wrote:
> When debugging a customer who couldn't load our site with an http
> connection (worked fine on ssl as it bypassed the firewall) we came
> across an issue where if we tried to load the *.cache.html file gwt
> was trying to load manually the companies firewall had displayed an
> error message. There was no error on the gwt side, so we were unable
> to provide feedback to the user.
>
> Is it possible to write something in the nocache.js that checks that
> the *.cache.html that is loaded is actually what we expect, and if
> not, we can get an error message back to the user in some way?
>
> Currently we use the following method for detecting load errors, but
> they aren't being called.  Could it be tied into this in some way?
>
> <meta name="gwt:onLoadErrorFn" content="loaderror"></meta>
> <meta name="gwt:onPropertyErrorFn" content="unsupported"></meta>
>
> <script type="text/javascript">
>                 <!--
>                         // Called when GWT is not supported
>                         function unsupported() {
>                                 document.getElementById('loading').className 
> = "loadError
> message-center-screen";
>                                 
> document.getElementById('loading-content').innerHTML = "Your
> browser is not supported. Please reload with a modern browser such as
> <a href=\"http://www.getfirefox.com\";>Firefox</a> or Internet Explorer
> Version 6 or Above.";
>                         }
>                         function loaderror(){
>                                 document.getElementById('loading').className 
> = "loadError message-
> center-screen";
>                                 
> document.getElementById('loading-content').innerHTML = "Error:
> There was a problem loading the application.";
>                         }
>                 -->
>         </script>
>
> E.g. a new meta property could be added that tells us the cache file
> is not able to be loaded, with the name of the cache file so we can
> show them the error by opening it in a new window so they can see the
> error message.
>
> Joe
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to