Issue Summary

When customer make an HTTP call to not existing resource Jira is returning 302 redirect HTTP code, despite user has valid logging credentials.

Steps to Reproduce

1. Use any http tool to make http calls.
2. Make a request using Basic Auth to non existing resource e.g. `http://localhost:2990/jira/rest/apsssdfsa/2/issue/DAJ-1`
3. Observe that Jira return `404` http code
4. Switch to any other authentication(easiest option is to generate access token for Jira account and use it as Bearer Token)
5. Make a request using new auth option to same resource as in the step 2: `http://localhost:2990/jira/rest/apsssdfsa/2/issue/DAJ-1`

Expected Results

404 HTTP code

Actual Results

302 HTTP redirect code to login page despite being able to authenticate user

Workaround

Currently there is no known workaround for this behaviour. A workaround will be added here when available