Re: [EsiGate-users] POSTs to non-origin provider

[Philippe De O. <phi...@gm...>]

Hi,

You are right. You must post directly to PHP system and declare a
esi:fragment for the required result. When using the esi:include, combine
it with a esi:replace so you will not have to split your CMS page.

BR,

On Mon, Nov 10, 2014 at 11:47 AM, Dave Sowerby <dav...@gm...>
wrote:

> Hi,
>
> I'm currently trying to work out how I might be able to solve a problem
> with a proof-of-concept using esigate that I've been working on.
>
> A have two providers:
>
> o A CMS which provides the theme and the page structure
> o A PHP system which provides fragments based upon the user's session.
>
> However, I need to use posts to the PHP system in order to handle form
> processing which is where my confusion arises.
>
> Just for clarity, here is my esigate.properties:
>
> origin.remoteUrlBase=http://www.cmsprovider.com
> origin.mappings=/*
>
> php.remoteUrlBase=http://www.phpprovider.com
> php.mappings=/php/*
>
> If I include the form through an ESI Include statement obviously
> everything then works fine for the initial rendering of the form in the
> resultant response.  However the form target has to be a /php/ based
> request so that the entities for the post are actually delivered to the
> provider.
>
> This PHP system can only produce fragments of the page and while I could
> split up the CMS page into fragments and include them that way it doesn't
> feel right to be doing this.
>
> Have I missed some element of the esi flow that would cover this use
> case?  Should I be posting directly and declaring a esi:fragment of the
> required result and an esi:include for the CMS page?
>
> Cheers,
>
> Dave.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>
>


-- 
Philippe De Oliveira