Thanks Kasun for looking into this..

On Fri, Jun 1, 2012 at 10:27 AM, Kasun Indrasiri <[email protected]> wrote:
> Hi Reka,
>
> I'm working on a fix for this issue.
>
>
> On Fri, Jun 1, 2012 at 10:25 AM, Reka Thirunavukkarasu <[email protected]>
> wrote:
>>
>> Hi,
>>
>> We have configured LB with AS in order to check the context mapping to
>> webapps. Since the context mapping is done through virtual host in AS,
>> we should be able to access virtual host (say testapp.wso2.com) from
>> browser with the url: https://testapp.wso2.com:9443/ where 9443 is the
>> AS-https port.
>>
>> So, when we have LB in front of AS, let's say 8280 is LB-https port,
>> then we can access the virtual host from LB like
>> https://testapp.wso2.com:8280/. But this falis, and redirecting to
>> carbon management consloe, since the Host header is overwritten with
>> host name from url (Eg: loacalhost) instead of actual host
>> information.
>>
>> But when we checked this with LB, after few modification in synapse,
>> Http host header is properly added. Even after that also, AS didn't
>> receive the actual host. Also, we experienced the same issue with Nio
>> and pass through transport as well. Since the host header is available
>> at LB level, this needs further invstigation in tranport level.
>>
>> We need to resolve it, since it is a blocker for accessing virtual host.
>>
>> So, the jira has been created: https://wso2.org/jira/browse/CARBON-13377
>>
>> Thanks,
>> Reka
>
>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to