[
https://issues.apache.org/jira/browse/TS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828919#action_12828919
]
Leif Hedstrom commented on TS-98:
---------------------------------
Another option, if the above changes are too extreme, would be to extend the
API to include a "length" header. This way, you don't have to make an
assumption about the string being NULL terminated, and you also don't have to
call strlen() on it twice (like now). You'd still have to store the "length"
somewhere, like you store the URL string.
I'm OK with either solution, my main "beef" here is to assume that the strings
are NULL terminated.
> 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.
