how to present an AJAX-intensive page through the SA4500?

[lightxx_]

hi guys!

so i've got an (in-house built) intranet web site here heavily relying on AJAX requests, which do not allow cross-domain scripting. this page should be presented through a SA4500 to a few selected outside users, and the SA should also do the authentication.

which means outside users MUST authenticate against the SA before they get the page in question delivered.

every AJAX request through the internal rewrite engine of course fails. we have enough public IPs to assign a dedicated IP just for this page to the SA. also, creating an external A-record named exactly as our internal A-record would be no problem (cross domain issues).

are there any best pratctice advises on how to present such a page? moreover, network connect is no option as we need to present this page to thin clients / mobile phones (iPhone Pulse client, anyone? ) as well.

any ideas?

thanks,

Tom

[kcorace_]

The only way we have been able to get this to work is through using the Pass Through Proxy feature and assigning that resource a different port. Even then we occasionaly run into formatting and other issues. I think it all depends on the various AJAX calls. I don't believe that we've tested it out through a phone though.

[lightxx_]

the problem with the Pass Through Proxy is that i lose authentication over the SA. sites presented through the proxy are always accessible, aren't they?

i find it rather disappointing that an every-day technology such as AJAX is still a problem for an appliance as expensive as the SA4500 after all, this is what they are built for. squid is free and open source and does a better job (transparently) proxying AJAX requests.

[zanyterp_ · Accepted solution]

There is nothing lost with passthrough proxy; what do you feel is lost by using this method? In order to access a site that is rewritten using the passthrough proxy engine rather than the core rewrite engine, users must login to the IVE and click on the bookmark link. Only at that time will the connection be valid to the resource; if the user attempts to connect directly without logging in, they will be forced to login.

Unfortunately, AJAX is not a set standard and it is also constantly evolving and the rewriting engine is constantly being updated to try and work with new items. You can open a JTAC case to see if they can help with finding a solution; it is possible there is something that can be fixed.

[lightxx_]

thank you very much for your reply. from reading the documentation (or rather the lack thereof when it comes to pass-through proxy) it seemed to me like the resources was always available, regardless if somebody signed in before.

thanks for clearing that up!

[zanyterp_]

You are welcome; glad I could help out.