Hi Sujanan,
As indicated in the issue, this bug was identified before and the fix is
available from version 1.0.40
You can get this fix by removing the siddhi-io-http-*.jar in the
{SP_HOME}/lib directory and add the latest version of the extension.
Best Regards,
*Niveathika Rajendran,*
*Senior Software Engineer.*
*Mobile : +94 077 903 7536*
On Thu, Dec 13, 2018 at 12:50 PM Sujanan Bhathiya <[email protected]> wrote:
> HI,
>
> As a part of project "TeleSign two-factor authenticator for IAM" which I
> was assigned, following strange behavior was identified while configuring
> the Stream Processor. In this scenario my goal was to configure the
> Identity Server for risk based adaptive authentication with the help of
> Stream Processor using an external API which means the risk score is
> fetched from a external API. In order to this to get succeed I wrote a
> Siddhi App using siddhi-io-http extension. First I checked with a mock API
> which is locally established for testing purposes and it worked correctly.
> Later I changed the "publisher.url" parameter in "http-request" type in
> @sink to remote API's URL and the response was a "400 Bad Request" from the
> remote server. Based on a offline discussion with Tishan we Identified
> that we should set a HOST header in our request to get a successful result.
> So he opened this issue
> <https://github.com/wso2-extensions/siddhi-io-http/issues/99>.
>
> For now as a workaround I set the host header manually and it worked. Any
> suggestions on this?
>
> --
> *Sujanan Bhathiya* | Intern | WSO2 Inc.
> (m) (+94) 710830823 | (e) [email protected]
> GET INTEGRATION AGILE
> Integration Agility for Digitally Driven Business
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
