[jira] [Updated] (TS-2213) Body log tags have a default value of "0", should they be "-1" now?
[ https://issues.apache.org/jira/browse/TS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2213: -- Labels: incompatible (was: compatibility) > Body log tags have a default value of "0", should they be "-1" now? > --- > > Key: TS-2213 > URL: https://issues.apache.org/jira/browse/TS-2213 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Leif Hedstrom > Labels: incompatible > Fix For: sometime > > > In our logging tags that provides a value for the body length, we default to > 0 in the absence of a value. This is somewhat bad now, because we actually > supports caching objects with a zero length body. Hence, it's not > distinguishable between a zero length body entry, or one where we couldn't > retrieve a body length (for whatever reason). > I'm wondering if we should change all the defaults for all "byte counts" in > logging from "0" to "-1"? This would be an incompatible change, so marking > this for v5.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2213) Body log tags have a default value of 0, should they be -1 now?
[ https://issues.apache.org/jira/browse/TS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2213: Fix Version/s: (was: 6.0.0) sometime Body log tags have a default value of 0, should they be -1 now? --- Key: TS-2213 URL: https://issues.apache.org/jira/browse/TS-2213 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Leif Hedstrom Labels: compatibility Fix For: sometime In our logging tags that provides a value for the body length, we default to 0 in the absence of a value. This is somewhat bad now, because we actually supports caching objects with a zero length body. Hence, it's not distinguishable between a zero length body entry, or one where we couldn't retrieve a body length (for whatever reason). I'm wondering if we should change all the defaults for all byte counts in logging from 0 to -1? This would be an incompatible change, so marking this for v5.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2213) Body log tags have a default value of 0, should they be -1 now?
[ https://issues.apache.org/jira/browse/TS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2213: -- Labels: compatibility (was: ) Body log tags have a default value of 0, should they be -1 now? --- Key: TS-2213 URL: https://issues.apache.org/jira/browse/TS-2213 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Leif Hedstrom Labels: compatibility Fix For: 6.0.0 In our logging tags that provides a value for the body length, we default to 0 in the absence of a value. This is somewhat bad now, because we actually supports caching objects with a zero length body. Hence, it's not distinguishable between a zero length body entry, or one where we couldn't retrieve a body length (for whatever reason). I'm wondering if we should change all the defaults for all byte counts in logging from 0 to -1? This would be an incompatible change, so marking this for v5.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2213) Body log tags have a default value of 0, should they be -1 now?
[ https://issues.apache.org/jira/browse/TS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-2213: --- Fix Version/s: (was: sometime) 6.0.0 Body log tags have a default value of 0, should they be -1 now? --- Key: TS-2213 URL: https://issues.apache.org/jira/browse/TS-2213 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Leif Hedstrom Fix For: 6.0.0 In our logging tags that provides a value for the body length, we default to 0 in the absence of a value. This is somewhat bad now, because we actually supports caching objects with a zero length body. Hence, it's not distinguishable between a zero length body entry, or one where we couldn't retrieve a body length (for whatever reason). I'm wondering if we should change all the defaults for all byte counts in logging from 0 to -1? This would be an incompatible change, so marking this for v5.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2213) Body log tags have a default value of 0, should they be -1 now?
[ https://issues.apache.org/jira/browse/TS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Farrell updated TS-2213: - Fix Version/s: (was: 5.0.0) Body log tags have a default value of 0, should they be -1 now? --- Key: TS-2213 URL: https://issues.apache.org/jira/browse/TS-2213 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Leif Hedstrom In our logging tags that provides a value for the body length, we default to 0 in the absence of a value. This is somewhat bad now, because we actually supports caching objects with a zero length body. Hence, it's not distinguishable between a zero length body entry, or one where we couldn't retrieve a body length (for whatever reason). I'm wondering if we should change all the defaults for all byte counts in logging from 0 to -1? This would be an incompatible change, so marking this for v5.0.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2213) Body log tags have a default value of 0, should they be -1 now?
[ https://issues.apache.org/jira/browse/TS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Farrell updated TS-2213: - Fix Version/s: 5.0.0 Body log tags have a default value of 0, should they be -1 now? --- Key: TS-2213 URL: https://issues.apache.org/jira/browse/TS-2213 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Leif Hedstrom Fix For: 5.0.0 In our logging tags that provides a value for the body length, we default to 0 in the absence of a value. This is somewhat bad now, because we actually supports caching objects with a zero length body. Hence, it's not distinguishable between a zero length body entry, or one where we couldn't retrieve a body length (for whatever reason). I'm wondering if we should change all the defaults for all byte counts in logging from 0 to -1? This would be an incompatible change, so marking this for v5.0.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
