This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Proxy Server Resource Provider

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Proxy Server Resource Provider

Excerpt
hiddentrue

Definition of a ResourceProvider infrastructure to enable supporting HTTP proxy functionality for Sling (DRAFT)

Status: DRAFT
Created: 10. January 2014
Author: fmeschbe
Issue: ---

Table of Contents
minLevel2

Sketch

  • Request Forwarding
  • Pluggable Transport Protocol proxying: Requests to Sling are always HTTP based; proxied requests may be HTTP, FTP, or others.
  • Pluggable Request and Response translation: Input requests can be translated to SOAP requests with responses translated back according to expected formats such as JSON, XML, HTML, etc.
  • Request URL mapping to proxied request URL (e.g. using URL templates)
  • Configuration defined in the repository for ResourceProvider services:
    • Resource Type indicating Proxy root; e.g. sling:resourceType = proxy
    • Proxy URL; e.g. proxyUrl=http://the.target.com
    • etc
  • ProxyResourceProvider controller registers ResourceProvider services based on the proxy configurations with the respective root addresses.
  • Example: ResourceProvider registered at /proxy
    • proxyUtl=http://the.target.com
    • Map /proxy.html ==> http://the.target.com/
    • Map /proxy/foo.html ==> http://the.target.com/foo