[
https://issues.apache.org/jira/browse/STRATOS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037492#comment-14037492
]
Nirmal Fernando commented on STRATOS-676:
-----------------------------------------
Hi Imesh,
Well, this is the HTTP spec, and what it explains is the HTTP protocol and
headers. Since, LB uses those headers, LB should respect the HTTP spec. I don't
understand why it is so surprising to you.
Point is Http spec clearly specify that the Location header will be used to
'redirect the recipient to a location other than the Request-URI'.
Rationale is why would you need to do even touch the Http Location header if
it's a host name? As the LB, it doesn't have any right/knowledge to change it.
eg:
LB fronts both PHP and Identity server clusters;
In LOCATION=identity.stratos.com/a/b
in HOST=php.stratos.com
and the issue is LB re-write the Location header with php.stratos.com.
> LB shouldn't be re-writing http location header if Location is a hostname
> -------------------------------------------------------------------------
>
> Key: STRATOS-676
> URL: https://issues.apache.org/jira/browse/STRATOS-676
> Project: Stratos
> Issue Type: Bug
> Components: Load Balancer
> Affects Versions: 4.0.0
> Reporter: Nirmal Fernando
> Assignee: Nirmal Fernando
> Priority: Critical
> Fix For: 4.1.0
>
>
> After investigating the issue I found out that Stratos LB re-writes Http
> Location Header even if the Location header is a host name. This violates the
> spec and break most of the real world scenarios.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
