Eric, thanks for getting back to me. I had the portlet on the page twice, then I later discovered other portlet's javascript interfering with other portlets.
Thanks again - all fixed. On Jan 30, 2013, at 10:46 AM, Eric Dalquist wrote: > Is the first request a HTTP HEAD? The proxy portlet needs to determine the > content type to figure out how to handle the content and so if it can't > determine the content type by how the url is used in the proxied page it does > a HTTP HEAD first looks at the content type and then does the HTTP GET. > > Also this should probably be on the uportal-user list. > > -Eric > > > On 1/30/13 9:15 AM, Brad Morse wrote: >> I created a web proxy porlet that fires two ajax calls when the portlet >> loads, when i view the app outside of the portal, it fires each one once, as >> seen in firefox firebug, but when I use it as a web proxy portlet in the >> portal, it fires both ajax calls twice. >> >> I edited the web proxy portlet settings and I only put in the URL in the >> Base URL under general configuration settings for the Portlet Administration >> Portlet page. >> >> uPortal v 3.2.4 >> >> Is there anything you could recommend me looking into? > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
