We're updating the issue view to help you get more done. 

REST-164 Implemented checking the X-Atlassian-Token header with the wrong value

Description

Instead of checking that a request has a header name 'X-Atlassian-Token' with a value of 'no-check' the code implemented in checks for a value of 'nocheck'. This differs from the accepted value of the 'X-Atlassian-Token' header and we should update the code to accept a value of 'no-check' as well as 'nocheck' to be consistent.

Environment

Testing Notes

Status

Assignee

David Black

Reporter

David Black

Fix versions

Priority

Minor