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
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Proxy Server Resource Provider

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

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
  • No labels