[ 
https://issues.apache.org/jira/browse/STRATOS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037331#comment-14037331
 ] 

Nirmal Fernando commented on STRATOS-676:
-----------------------------------------

What else than HTTP spec :-) Most of the real world cases you use host names. 
And especially if you send via a LB, you must use host names as a best practice.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
14.30 Location

The Location response-header field is used to redirect the recipient to a 
location other than the Request-URI for completion of the request or 
identification of a new resource. For 201 (Created) responses, the Location is 
that of the new resource which was created by the request. For 3xx responses, 
the location SHOULD indicate the server's preferred URI for automatic 
redirection to the resource. The field value consists of a single absolute URI.

       Location       = "Location" ":" absoluteURI

An example is:

       Location: http://www.w3.org/pub/WWW/People.html

      Note: The Content-Location header field (section 14.14) differs
      from Location in that the Content-Location identifies the original
      location of the entity enclosed in the request. It is therefore
      possible for a response to contain header fields for both Location
      and Content-Location. Also see section 13.10 for cache
      requirements of some methods.


> 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)

Reply via email to