Doc changes for no NULL terminated strings, and one API rename
--------------------------------------------------------------
Key: TS-581
URL: https://issues.apache.org/jira/browse/TS-581
Project: Traffic Server
Issue Type: Bug
Components: Documentation
Reporter: Leif Hedstrom
Fix For: 3.0
We have eliminated the code that allowed a few APIs to assume that strings were
NULL terminated, when we really don't make any such promises. Below is the list
of APIs that are affected, we should make sure all documentation makes a point
that the strings are not NULL terminated, and that the length pointer argument
must not be NULL. In particular these two APIs have the wrong (old)
documentation:
INKHttpHdrMethodGet()
INKMimeHdrFieldValueStringGet()
-- Leif
const char * TSUrlSchemeGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSUrlUserGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSUrlPasswordGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSUrlHostGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSUrlPathGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSUrlHttpParamsGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSUrlHttpQueryGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSUrlHttpFragmentGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSMimeHdrFieldNameGet(TSMBuffer bufp, TSMLoc hdr, TSMLoc field, int
*length);
const char *TSHttpHdrMethodGet(TSMBuffer bufp, TSMLoc obj, int *length);
const char *TSHttpHdrReasonGet(TSMBuffer bufp, TSMLoc obj, int *length);
TSReturnCode TSMimeHdrFieldValueStringGet(TSMBuffer bufp, TSMLoc hdr, TSMLoc
field, int idx, const char **value_ptr, int *value_len_ptr);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
