You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/02/02 21:50:25 UTC

[jira] Commented: (TS-98) trafficserver should follow redirects when a special header is provided

    [ https://issues.apache.org/jira/browse/TS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828759#action_12828759 ] 

Leif Hedstrom commented on TS-98:
---------------------------------

Talking to Wendy, I'm wondering if this new API should be slightly different. First of all, I'm not keen on sending in the string, and assuming it's NULL terminated. Almost all APIs in TS don't make such assumption. But to be even more "consistent", I think the APIs should be something in line with

   inkapi INKMLoc            INKRedirectUrlGet(INKHttpTxn txnp);
   inkapi INKReturnCode      INKRedirectUrlSet(INKHttpTxn txnp, INKMLoc url);


(or some such, not saying this is the way it should be, but something in line with how the other API functions deal with URLs). Then in the code, you dont' have to use strlen() to get URL lengths, or make assumptions that the "string" is NULL terminated.

Thoughts?

> 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, 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.