Portal, V6.1
The programming model for using the AJAX proxy
This topic describes how you use the proxy when programming portlets. The programming model specifies the following:
- How you make requests, that is how you format URLs that address the proxy
- How the proxy reacts in specific cases, for example in case of an error.
The proxy does not rewrite URLs that are part of the received content, because the proxy does not know the semantics of the content that it fetches. Consequently, AJAX applications that use the proxy need to generate proxy
URLs by themselves.
- URL format and examples
The proxy can be addressed via URLs that comply with the REST-based URL format given here.- AJAX proxy status codes
The AJAX proxy responds to requests by defined status codes. Possible errors that can occur in the proxy are mapped to the corresponding HTTP status codes.- AJAX proxy authentication
The AJAX proxy is integrated with the Credential Vault of the portal. The Credential Vault stores user credentials, such as user IDs and passwords. The integration allows portlets to log in to applications outside of portal. By using the Credential Vault, the proxy can retrieve the credentials of a user and then pass this information to a target host for authentication.- Use the AJAX proxy in portlets
Here is how you use the AJAX proxy in portlets.
Parent topic
HTTP proxy for AJAX applications