Looking for something that's not here? Let us know: support@tiggzi.com
Documentation‎ > ‎Services‎ > ‎REST Service‎ > ‎

Using Tiggr Proxy



Tiggr Proxy makes it very easy to use REST API which which doesn't support jsonp. When invoking any REST service, there is a built in security feature that's always on. The security features says that a page from loaded from domain myhost.com can only invoke services from the same domain, myhost.com. This is to ensure that no one can inject any bad JavaScript into your page and invoke a bad service from another server. 

When building a mobile app in Tiggr, the mobile screen is loaded from gotiggr.com domain but the REST service you invoking is residing on a different domain (for example yourcompany.com). This is the same problem as described above.  To help solve this problem, Tiggr now has Tiggr Proxy. When Tiggr Proxy is turned on, the request is routed via Tiggr server, instead of being invoked directly from the page. Because the service is now invoked from Tiggr server, and not from a Weeb page, cross-domain security doesn't play a role. 

Note: Tiggr Proxy only works when using json method.