PDA

View Full Version : Explorer demo doesn't work behind a proxy



zaccret
29 Apr 2008, 2:21 AM
Hi,

I cannot see the Explorer demo, my browsers (Firefox 2 or 3) stay on "Loading demo".
I am behind a proxy. May it be the reason ?

gslender
29 Apr 2008, 2:24 AM
might be... its working fine for me... FF2 and IE7

zaccret
29 Apr 2008, 2:28 AM
Thanks for your answer. For me, it doesn't work anymore on IE. On the other side, gwt-ext demo is working

darrellmeyer
29 Apr 2008, 8:21 PM
I really do not think this is a bug with the Ext GWT code. This sounds like some sort of env issue. I am moving this post to help.

jamestasc
30 Apr 2008, 7:27 AM
I can not get the explorer demo to display in Safari on the mac.

Firefox displays OK from the same machine.

JT

zaccret
5 May 2008, 11:04 PM
By the way, ExtJS demo/samples is working perfectly. But Ext GWT Explorer is still not working on my Firefox or IE (Windows XP). :((

cdasher
6 May 2008, 7:07 AM
Not sure if this is related, but I have a content panel (BorderLayout) with some forms in it (kindof complicated layout) inside a Window. It works in Firefox 1.5.0.3 running on RedHat EL 4 , However the same page only shows the window and none of my nested content on IE 7

cdasher
6 May 2008, 7:56 AM
In fact, the following code works correctly under firefox and linux but the TOP DEVICE FORM does not show up under IE 7 windows


Window window = new Window();
window.setMaximizable(false);
window.setResizable(false);
window.setShadow(false);
window.setModal(true);
window.setLayout(new BorderLayout());

// CREATE NORTH
BorderLayoutData northdata = new BorderLayoutData(LayoutRegion.NORTH,
0, 0, 0);
northdata.margins = new Margins(0, 0, 0, 0);
northdata.collapsible = false;

ContentPanel northFormPanel = new ContentPanel();
northFormPanel.setData(northdata);
northFormPanel.setCollapsible(false);
northFormPanel.setHeaderVisible(false);
northFormPanel.setBorders(false);

// CREATE CENTER
BorderLayoutData centerdata = new BorderLayoutData(LayoutRegion.CENTER,
300, 300, 300);
centerdata.margins = new Margins(0, 0, 0, 0);
centerdata.collapsible = false;

ContentPanel centerFormPanel = new ContentPanel();
centerFormPanel.setData(centerdata);
centerFormPanel.setHeaderVisible(false);
centerFormPanel.setCollapsible(false);
centerFormPanel.setLayout(new FlowLayout());


centerFormPanel.setBorders(false);

//CREATE TOP DEVICE FORM

FormPanel topDeviceForm = new FormPanel();
topDeviceForm.setHeaderVisible(false);
topDeviceForm.setBorder(true);

final TextField nameField = new TextField();
nameField.setEmptyText("Name");
nameField.setFieldLabel("Name");
nameField.setAllowBlank(false);
topDeviceForm.add(nameField);
topDeviceForm.layout(true);
centerFormPanel.add(topDeviceForm);
centerFormPanel.layout(true);

//END CREATE TOP DEVICE FORM

// CREATE EAST
BorderLayoutData eastdata = new BorderLayoutData(LayoutRegion.EAST,
200, 200, 200);
eastdata.margins = new Margins(0, 0, 0, 0);
eastdata.collapsible = false;

ContentPanel eastFormPanel = new ContentPanel();
eastFormPanel.setData(eastdata);
eastFormPanel.setCollapsible(false);
eastFormPanel.setHeaderVisible(false);
eastFormPanel.setBorders(false);
eastFormPanel.setLayout(new FillLayout());

// CREATE SOUTH
BorderLayoutData southdata = new BorderLayoutData(LayoutRegion.SOUTH,
50, 50, 50);
southdata.margins = new Margins(0, 0, 0, 0);
southdata.collapsible = false;

ContentPanel southFormPanel = new ContentPanel();
southFormPanel.setData(southdata);
southFormPanel.setHeaderVisible(false);
southFormPanel.setBorders(false);
southFormPanel.setCollapsible(false);
southFormPanel.setLayout(new FillLayout());

HorizontalPanel southFormButtonPanel = new HorizontalPanel();
southFormButtonPanel.setStyleAttribute("padding", "10");

southFormPanel.add(southFormButtonPanel);


// CREATE WEST
BorderLayoutData westdata = new BorderLayoutData(LayoutRegion.WEST, 0,
0, 0);
westdata.margins = new Margins(0, 0, 0, 0);
westdata.collapsible = false;

ContentPanel westFormPanel = new ContentPanel();
westFormPanel.setData(westdata);
westFormPanel.setHeaderVisible(false);
westFormPanel.setBorders(false);
westFormPanel.setCollapsible(false);

window.add(centerFormPanel);
window.add(northFormPanel);
window.add(southFormPanel);
window.add(eastFormPanel);
window.add(westFormPanel);
window.setHeight(500);
window.setWidth(550);
window.setMinHeight(500);
window.setMinWidth(550);
window.layout(true);
window.show();

zaccret
13 May 2008, 12:28 AM
darell, could the explorer demo be downloadable ?

zaccret
13 May 2008, 12:33 AM
Apologies, it is already in the beta 2 sdk :">

zaccret
29 May 2008, 10:10 PM
Actually, I have the same issue with gwt 1.5 rc1 release : I can't see release notes and documentation. At home, I can. :((

Dave_N_Finch
11 Jun 2008, 11:17 PM
I have the same problem - at work (behind a proxy) i can't access the demo of RC4 or RC5.
The problem is the same in IE6 & FF2. I have tried clearing my cache and disabling Firebug.

The error is reported to be on line 4106 - function wke(a){if(a<=30){return 1&lt;<a}else{return wke(30)*wke(a-30)}}

I am hoping to use GXT but my site needs to be accessible to people behind firewalls so I hope this gets resolved soon.

Dave

Dave_N_Finch
13 Jun 2008, 2:53 AM
I have discovered a work around, using https rather than http works fine.

I guess this confirms that it is something that the proxy is doing that corrupts the JS

zaccret
13 Jun 2008, 3:00 AM
:((it doesn't work for me but it gives me a new javascript error :

invalid XML tag syntax
function wke(a){if(a<=30){return 1&lt;<a}else{return wke(30)*wke(a-30)}}\n
190DCF8CBFAF7B371...cache.html (line 4106)I guess this won't help...

zaccret
20 Oct 2008, 4:19 AM
I guess this is a GWT bug. Any possible workaround ?

zaccret
20 Oct 2008, 4:23 AM
Actually, with Firebug, I see the same JS error with either http or https

Dave_N_Finch
20 Oct 2008, 8:33 AM
Hi Zaccret,

Looks like the same problem as I am having. My assumption is that the &lt; should be <.

I am sure it is not an Ext issue and maybe not even a GWT issue. I have post an issue on the GWT issue tracker but have not had much response.

My theory is that a proxy is corrupting the javascript rather than there being an actual bug in the software but i am hoping that something can be done about it.

This problem seems to effect more and more GWT apps but it doesn't seem that very many people are affected.

I think my employer uses webwasher, do you know what proxy you are using?

The only solution I have found is to use https rather than http, this obviously depends on the server and does work with the demos on www.extjs.com but not any GWT apps hosted by google.

regards,
Dave

gslender
20 Oct 2008, 1:27 PM
don't ya think the proxy or firewall that is incorrectly mangling web pages is kinda the fault/problem? :-?

do you know why the proxy/firewall does this? is it supposed to (ie does the vendor/supplier agree that this activity is normal?)

zaccret
21 Oct 2008, 1:24 AM
I think my employer also uses webwasher. The https workaround doesn't work for me. I don't know what to do.
It would be nice if we were able to download the samples. Then I could deploy them on my machine.

darrellmeyer
21 Oct 2008, 6:24 AM
You can. Try the samples folder from the build.

Dave_N_Finch
21 Oct 2008, 10:12 AM
The thing that really worries me is developing an application and then finding that some people can't use it because of the proxy that their employer happens to use.
:(

gslender
21 Oct 2008, 2:53 PM
Unless this is a wide spread issue (ie GWT doesn't work behind ANY common proxy or firewalls) I'd suggest the employer or organization using a proxy that "changes" the actual HTML to the point that it breaks Ajax applications is the problem. Not the Ajax application.

Is it possible to find out what exactly is being changed and why? Surely these proxy/firewall applications log or alert that they needed to modify the website code being sent to the browser? I can't imagine that this is a common issue - is it?

Here's a post where another company, that makes some kind of trust toolbar is being incorrectly filtered by webwasher. http://forums.comodo.com/trusttoolbar/blocked_by_webwasher-t2350.0.html

As with most security products, it probably has a few false positives that incorrectly stop things it shouldn't. I can't really say GWT or ExtGWT should accomodate a product that doesn't do what its supposed to do... ie stop bad things and let good things in.

Cheers,
Grant

zaccret
29 Oct 2008, 1:58 AM
I agree with you, it is not GWT or Ext's fault. But it doesn't seem to be specific to Webwasher : http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/e0f017875d5c34bb# (a guy is talking about Symantec). Anyway, unfortunately it is not so easy for someone in a very big company to ask to change firewall rules because of a single GWT app, it can takes some time (and we must find the rule to change) :">

@Darell : Thanks. ACTUALLY, there IS a samples folder in the gxt bundle. :"> So that's OK for me.

gslender
29 Oct 2008, 2:26 AM
...a quick way to know for sure is to access via HTTPS whereby the firewall cannot change or alter the content - as its encrypted it can't mess with anything. :P

So try this... https://www.extjs.com/explorer/

zaccret
30 Oct 2008, 1:01 AM
Unfortunately, as I said above, it doesn't work for me, I get a javascript error :

invalid XML tag syntax
function Euf(a){if(a<=30){return 1&lt;<a}else{return Euf(30)*Euf(a-30)}}\n