trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Call (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TS-98) trafficserver should follow redirects when a special header is provided
Date Wed, 17 Feb 2010 21:41:27 GMT

     [ https://issues.apache.org/jira/browse/TS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryan Call updated TS-98:
-------------------------

    Attachment: redirect_bcall_001.patch

Updated the patch file to remove the prototype of INKHttpTxnCreateRequest from the header
file and the comment of it ever existing in the InkAPI.cc.

APIs that have been deprecated, but still exist should be in the header file.  If we are going
to remove the API then there is no reason for it to be in the header.

> trafficserver should follow redirects when a special header is provided 
> ------------------------------------------------------------------------
>
>                 Key: TS-98
>                 URL: https://issues.apache.org/jira/browse/TS-98
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Wendy Huang
>            Assignee: Bryan Call
>             Fix For: 2.0.0a
>
>         Attachments: code_diff.txt, new_TS-98.patch, redirect_bcall_001.patch, TS-98.patch
>
>
> Some people need a service such that if the Origin Server (OS) returns back a particular
HTTP
> response code or HTTP response header, TS simply redirects the request to another Origin
Server and serves the
> response that the new OS responds with. 
> it is prefered to be a response header instead of a response error code, since changing
the meaning of an
> existing http response error code is undesirable.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message