406 NOT ACCEPTABLE

The objective asset doesn’t have a present representation that would be worthy to the client specialist, as per the proactive exchange header fields got in the request, and the server is reluctant to supply a default representation. 

The server SHOULD produce a payload containing a rundown of accessible representation qualities and comparing asset identifiers from which the client or client specialist can pick the one generally fitting. A client operator MAY naturally choose the most suitable decision from that rundown. In any case, this particular doesn’t characterize any standard for such programmed determination, as depicted in RFC7231 Section 6.4.1.

Leave a Reply