Traffic draft_policy_decision display is different from PCE

[shara0620]

Although we are using the latest Workload, draft_policy_decision may be different between PCE and Workloader.

I would like to see the process changed so that the header is “Accept: application/json” in Workloader as in PCE and the conversion from json to CSV is done in Workloader.

[brian1917]

@shara0620 - I'm not sure this would affect draft policy decision. The PCE should be attaching the draft policy decision to the generated CSV if the --draft flag is set (and you are on a PCE that supports this API parameter. What exact behavior are you seeing?

[shara0620]

@brian1917 - Thank you for confirming.

The actual behavior is that the draft_policy_decision is displayed when the -draft flag is set, but
However, the draft_policy_decision was sometimes different from the draft_policy_decision displayed in PCE traffic.
This also occurred when downloading traffic from PCE.

The following information is based on my research and assumptions.
I think some of the request headers are different in each of the following movements.
・Traffic display with PCE
"Accept: application/json"
・Download traffic from PCE
"Accept: /"
・Workloader
"Content-type: application/json"

If you try it with the API, it will return JSON if "Accept: application/json".
Others will be returned as CSV.
Therefore, I believe there is a difference in the generation of draft policy decisions depending on whether they are returned in JSON or CSV.

As far as I've tried it, I've assumed the case of the policy decision indicated in PCE, so I requested a change from the method of obtaining CSV to the method of obtaining JSON like PCE.