You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/06/28 21:38:58 UTC

[GitHub] rob05c edited a comment on issue #2484: All API responses seemingly in violation of POSIX standards

rob05c edited a comment on issue #2484: All API responses seemingly in violation of POSIX standards
URL: https://github.com/apache/trafficcontrol/issues/2484#issuecomment-401181539
 
 
   The Traffic Ops API doesn't return POSIX files or lines. It serves JSON over HTTP. But neither of those standards are related to POSIX, operating systems, or filesystems of any kind. The API conforms to RFC2616 (, RFC7231, et al) for HTTP, and RFC7159 and RFC4627 for JSON. 
   
   If you're using the APIs in a POSIX context, for example piping `curl` results to POSIX utilities, you can use an intermediary tool like `jq` or `printf` to manipulate the output to be a POSIX-compliant file, e.g. `curl | xargs -I '{}' printf '{}\n'`.
   
   I'm not sure why you expect an HTTP-JSON API to be POSIX compliant, as they're entirely unrelated standards. Can you point to an HTTP or JSON RFC requiring or recommending POSIX compliance?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services