Virtualizing JavaScript calls

fiquebem

Setting: TS 6.5 SP2 on Solaris 8.

I am trying to get Interwoven's Proxy server to remap external URLs such as https://devpbgapp1.mycorp.com/POC... to a script within TeamSite such as my_virtualization.cgi.

Those URLs would appear in JavaScript/AJAX/XMLHttpRequest calls to retrieve JSON objects.

Here's what I'd like to do:

_regex=(https://devpbgapp1.mycorp.com/POC\?action=get_product_info&product_id=(\d+))=/iwbin/iw_cgi_wrapper.cgi/my_virtualization.cgi?product_id=$2&original_url=$1

Looks like that won't work in the [iwproxy_preconnect_remap] and [iwproxy_preconnect_redirect] configuration sections.

If I follow the instructions in the "Redirecting Fully Qualified URLs" section of the TeamSite Administration Guide (and make use of [iwproxy_fullproxy_redirect]), we'd have to configure our Web browsers to proxy through TeamSite. Changing one's browser doesn't seem practical, but would it work for JavaScript calls? What if the calls weren't fully-qualified (i.e., if they were URIs instead of URLs)? Then I guess they'd point back from the browser to the TS server, where iwproxy could remap them.

Any other thoughts?

Thanks,

S.

Adam Stoller

Setting: TS 6.5 SP2 on Solaris 8. I am trying to get Interwoven's Proxy server to remap external URLs such as https://devpbgapp1.mycorp.com/POC... to a script within TeamSite such as my_virtualization.cgi. Those URLs would appear in JavaScript/AJAX/XMLHttpRequest calls to retrieve JSON objects. Here's what I'd like to do: _regex=(https://devpbgapp1.mycorp.com/POC\?action=get_product_info&product_id=(\d+))=/iwbin/iw_cgi_wrapper.cgi/my_virtualization.cgi?product_id=$2&original_url=$1 Looks like that won't work in the [iwproxy_preconnect_remap] and [iwproxy_preconnect_redirect] configuration sections. If I follow the instructions in the "Redirecting Fully Qualified URLs" section of the TeamSite Administration Guide (and make use of [iwproxy_fullproxy_redirect]), we'd have to configure our Web browsers to proxy through TeamSite. Changing one's browser doesn't seem practical, but would it work for JavaScript calls? What if the calls weren't fully-qualified (i.e., if they were URIs instead of URLs)? Then I guess they'd point back from the browser to the TS server, where iwproxy could remap them. Any other thoughts? Thanks, S.

I won't claim to be an expert in proxies - but perhaps you're looking in the wrong place? Since this is a fully-qualified URL and you don't want to have to force your TS users to change their desktop browsers to use iwproxy - why not look into making a redirect (or proxy, or something) setting in the customer webserver's config file (i.e. in IIS on Windows or whatever web server you're using on Unix) - The effect of the proxy would be localized to the web server whose only purpose is to render virtualized content from TeamSite.