On Tue, Apr 7, 2015 at 9:35 PM, Sumedha Rubasinghe <[email protected]> wrote:
> Sajith, > Can you make this only applicable to selected web apps only? > No need of doing this. :) The handler will be added to main sequence. That is where all unresolved requests would go. > > On Tue, Apr 7, 2015 at 8:41 PM, Sajith Abeywardhana <[email protected]> > wrote: > >> Hi All, >> >> If webpage containing relative path content there is a problem in gateway >> side in AppM. Please find the full analysis in dev mailing list - >> "[Dev][AppM]App Manager Gateway Test". >> Here is the solution for the problem. By using custom mediator we >> re-write the all relative path request back to the client(web browser) with >> the gateway end point. >> >> Architecture Diagrams >> >> >> Below is the architecture diagrams for the solution. >> >> >> >> >> >> Main tasks to complete >> >> 1. Load all application from the database when starting the AppM >> server. Cache the application context and version as a ArrayList. >> 2. Write custom mediator class which we use to set the *referer *header. >> In this class we have to read the cached context+version list. >> 3. Re-write the Location header in main sequence and set the HTTP_SC >> as 303. >> >> >> Please be kind enough to provide feedbacks on anything need to be added >> or removed from the above. >> >> *Sajith Abeywardhana* | Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka. >> Mobile: +94772260485 >> Email: [email protected] <[email protected]> | Web: www.wso2.com >> > > > > -- > /sumedha > m: +94 773017743 > b : bit.ly/sumedha > -- /sumedha m: +94 773017743 b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
