HTTP proxy configuration

Some portlets use IBM WebSphere Portal resources to support HTTP proxy. Loading and caching remote URLs (such as RSS streams or HTML files) is done in the portal by the URL Manager service. If we specify an HTTP proxy in the configuration of the service, all remote requests are loaded using this HTTP proxy. This feature enables servers behind a firewall with no direct access to the Internet to load external data, such as news or stock information.

To configure WebSphere Portal for HTTP proxy, we use the WP PortletServiceRegistryService property in the portal WP Content Access Service in the WAS console. See the topic about Content Access Service and go to the section about Proxy protocol and port settings.

Parent Configure portal behavior