OASIS Open Mailing List Archives  ·  All Lists  ·  sarif  ·  2019-04

sarif — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

#378: request failure properties


I created and merged a change draft for Jim’s Issue #378 , “Add properties to describe failed requests”. https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-378-request-failure-properties.docx After feedback from MS, we accepted Jim’s original proposal to put the properties on the webResponse object. I chose the name noResponseReceived for the Boolean property. Rather than introducing a new property failureMessage , I overloaded the existing webResponse.reasonPhrase property (which normally holds, for example, "OK" on 200 or "Not found" for 404) to hold the failure message in the “no response received” case. Please take a look! Next is Yekaterina’s Issue #381 , “Associate descriptor metadata with thread flow locations”. (This is the “helper rule” feature.) Larry

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]