As an aside, the method name doesn't reflect exactly what I *think* it does...
If it is not too late, consider refactoring to DFUGetFileDefinition (or something to that affect)
Also, what is the "Format" request field for?
Conclusion
None
Activity
Show:
Anthony Fishbeck October 26, 2017 at 10:07 PM
The "http_content("application/octet-stream")" bit makes this a special method. A simple HTTP get call will return the content in the HTTP body. No XML wrapper. Think of it like an HTTP GET that returns a JPEG.. you don't want anything else in the body.
Kanghua Wang October 26, 2017 at 8:08 PM
The return value is binary due to:
Rodrigo Pastrana October 26, 2017 at 7:41 PM
Thanks . Since it has been around for so long, refactoring the method is out of the question. We definitely should either make Format optional (default the format), or reject the requests without format specified. However, I did notice the returned value is binary, does it make sense to return raw xml if format is not specified?
At any rate, this is low priority.
Kanghua Wang October 26, 2017 at 7:12 PM
The method has been there since OSS day1. It is used by ECLWatch UI (the DEF tab on the Logical File Details page). The "Failed to parse XSLT source" error is shown when an invalid string is in the "Format" request field. The "Format" request field can be either "def" or "xml". Possible fix may be using ESPenum string for the field.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
submitted several requests to WsDfu::DFUDEFFILE and received:
"Failed to parse XSLT source"
sample: http://<190IP>:8010//WsDfu/DFUDefFile?form&ver_=1.36&.Name=thor%3A%3Aicecream%3A%3Aicecream1
As an aside, the method name doesn't reflect exactly what I *think* it does...
If it is not too late, consider refactoring to DFUGetFileDefinition (or something to that affect)
Also, what is the "Format" request field for?