Ajax Proxy - Revision history

Rwest at 00:35, 8 March 2010

2010-03-08T00:35:36Z

2010-03-07T23:09:19Z

‎Example

2010-03-07T20:11:03Z

‎Overview

2009-12-19T23:49:35Z

‎Security

2009-12-19T23:49:24Z

‎Security

2009-12-19T23:47:53Z

‎Usage

2009-12-19T23:47:23Z

‎Overview

2009-12-19T23:47:04Z

‎Overview

2009-12-19T23:43:13Z

2009-12-18T16:35:11Z

‎Security

@@ Line 27: / Line 27: @@
 </pre>
-== Configuring==
+== Moving Ajax Proxy ==
-To start using the Ajax Proxy, be sure to copy the ajaxProxy.cfm located in /ADF/core/site-sample/ into your sites /_cs_apps/ directory.  Additionally, make sure that in your ADF.cfc (located in your /_cs_apps/ directory) you have the following line in your init() method:
+As a part of the installation of the ADF you were required to copy the ajaxProxy.cfm located in /ADF/core/site-sample/ into your sites /_cs_apps/ directory.  Additionally, you copied ADF.cfc (located in your /_cs_apps/ directory) into the same directory (/_cs_apps).
   setAjaxProxyURL("#request.site.csAppsWebURL#ajaxProxy.cfm");
-After the "loadSite()" call, make sure you [[Reset ADF|Reset your Site ADF]].
+change to:
 == Security ==

@@ Line 12: / Line 12: @@
 == Example==
 <pre>
 jQuery.get("#application.ADF.ajaxProxy#",
@@ Line 20: / Line 21: @@
      function( results ) ...
 });
 </pre>

@@ Line 1: / Line 1: @@
 ==Overview==
-Ajax Proxy is a CFM file located in the /_cs_apps/ directory of your site (copy from the /ADF/core/site-sample/) directory.  The concept of the Proxy is to have a single endpoint for all ajax calls into the ADF library and/or Apps that are built.  The goal with this single endpoint is two-fold:
+Ajax Proxy is a CFM file located in the /_cs_apps/ directory of your site (Note: this file was copied from the /ADF/core/site-sample/ directory as a part of installation) directory.  The concept of the Proxy is to have a single endpoint for all ajax calls into the ADF library and/or Apps that are built.  The goal with this single endpoint is two-fold:
 # Control security access to the methods within the ADF
 # Load the site application space so library and app calls have site level context

@@ Line 31: / Line 31: @@
 By default all methods within an application or the ADF library are locked down.  To make a method available you must add it to either your applications [[Proxy White List | Proxy White List]] (recommended) or the global [[Proxy White List | Proxy White List]].
-If your method performs potentially dangerous actions, you may also want to ensure the call is being conducted by a licensed contributor or a site admin.
+If your method performs potentially dangerous actions, you may also want to verify the call is being conducted by a licensed contributor or a site admin.
 [[Category: Security]]

@@ Line 31: / Line 31: @@
 By default all methods within an application or the ADF library are locked down.  To make a method available you must add it to either your applications [[Proxy White List | Proxy White List]] (recommended) or the global [[Proxy White List | Proxy White List]].
-If your method preforms potentially dangerous actions, you may also want to check to ensure that the call is being conducted by a licensed contributor or a site admin.
+If your method performs potentially dangerous actions, you may also want to ensure the call is being conducted by a licensed contributor or a site admin.
 [[Category: Security]]

@@ Line 5: / Line 5: @@
 ==Usage==
-To use the Ajax Proxy in a jQuery get/post call do the following:
+To use the Ajax Proxy in a jQuery get/post call, do the following:
 # URL to call is #application.ADF.ajaxProxy#
 # Add in the name of the bean you want to call

← Older revision		Revision as of 23:43, 19 December 2009
Line 32:		Line 32:

	If your method preforms potentially dangerous actions, you may also want to check to ensure that the call is being conducted by a licensed contributor or a site admin.		If your method preforms potentially dangerous actions, you may also want to check to ensure that the call is being conducted by a licensed contributor or a site admin.
		+
		+	[[Category: Security]]

← Older revision		Revision as of 16:35, 18 December 2009
Line 31:		Line 31:
	By default all methods within an application or the ADF library are locked down. To make a method available you must add it to either your applications [[Proxy White List \| Proxy White List]] (recommended) or the global [[Proxy White List \| Proxy White List]].		By default all methods within an application or the ADF library are locked down. To make a method available you must add it to either your applications [[Proxy White List \| Proxy White List]] (recommended) or the global [[Proxy White List \| Proxy White List]].

−	~~You should also become familiar with the [[CSSecurity_1_0\| CS Security v1]] component.~~ If your method preforms potentially dangerous actions, you may also want to check to ensure that the call is being conducted by a licensed contributor or a site admin.	+	If your method preforms potentially dangerous actions, you may also want to check to ensure that the call is being conducted by a licensed contributor or a site admin.