Description

The process listing, description, and job listing all have HTML responses support. However, when listing jobs (/jobs?f=html or by default when in a browser), the provided links of the listed JobID point to /jobs/{jobID}?f=html. Since HTML is not implemented for that endpoint, Weaver's own references result in 406, and users are forced to manually set f=json to obtain the status contents as JSON.

To Do

• Implement the Job Status response as HTML, such that the UI navigation in browsers is more natural.
• Given that jobs contain many other sub-paths, not all easily represented by HTML, they should ensure to omit the f=html (or maybe even explicitly set f=json?).

References

• relates to https://crim-ca.atlassian.net/browse/GD-571