Hi Tishan As I understand the issue is not related to CORS. basically what is failing here is that log-analyzer-proxy.jag <https://localhost/apimanager/admin/modules/la/log-analyzer-proxy.jag?type=14&tableName=LOGANALYZER> script is not exposed via revers-proxy or the script path is not re-written correctly by the application.
1. Is the log-analyzer-proxy.jag <https://localhost/apimanager/admin/modules/la/log-analyzer-proxy.jag?type=14&tableName=LOGANALYZER> hard-coded in a script ? 2. Check if you can access the log-analyzer-proxy.jag <https://localhost/apimanager/admin/modules/la/log-analyzer-proxy.jag?type=14&tableName=LOGANALYZER> after providing the mapped domain. 3. If above is working you can dynamically generate the script path in the app based on the revers-proxy config. Cheers Jo On Wed, Aug 24, 2016 at 7:49 AM, Tishan Dahanayakage <[email protected]> wrote: > Hi all, > > I am testing reverse proxy support in APIM log analyzer dashboard and came > though encountered following issue. > > When loading the gadgets we make the following call. > https://localhost/apimanager/admin/modules/la/log-analyzer- > proxy.jag?type=14&tableName=LOGANALYZER > > Because of the reverse proxy configuration origin and the request URL > domain does not match. This results in a CORS preflight request to the > destination. But since cookies are not allowed in preflight request, > jsessionID is not sent. This results in a redirection to login page. > Because of the redirection status code, preflight request is failed. > > Patching BE jaggery file to handle the OPTIONS preflight call will solve > this issue AFAIU. Is it the way we practice in /store /publisher? Or is > there any other way to avoid origin mismatch? > > Thanks > /Tishan > > -- > Tishan Dahanayakage > Senior Software Engineer > WSO2, Inc. > Mobile:+94 716481328 > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, re-transmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * <http://lk.linkedin.com/in/rumeshbandara>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
