title: Artifact URL on Nexus with Basic Auth
body: <p>I have two Nexus instances <code>2.0</code> and <code>2.11.4-01</code>. On the older one, when browsing to the URL (using a desktop browser):</p>
  
  <pre><code>https://nexus.example.com/content/repositories/company-releases/com/company/projectname/projectname-web/1.6.1-RC2/projectname-web-1.6.1-RC2.war
  </code></pre>
  
  <p>prompts for username and password with a <code>Basic-Auth</code> which is just what I want. I tried to accomplish the same on the newer version of Nexus and the browser does not prompt for username and password. Instead a page with the following message is displayed:</p>
  
  <blockquote>
    <p>Access Denied
    Please login before attempting further requests.</p>
  </blockquote>
  
  <p>The "login" is linked to authentication page on the Nexus UI. This is bad in my case because I am sending an artifact URL to the customer and she/he only need to provide username and password and the artifact is downloaded. I cannot now instruct all of them to use the UI login and navigate to the artifact.</p>
  
  <p>Is something wrongly configured on the newer version of my Nexus instance? Or maybe something changed in that area between these versions I have?</p>
  
  <p><strong>Edit</strong></p>
  
  <p>I realized that CURL is getting the following response header:</p>
  
  <pre><code>WWW-Authenticate: BASIC realm="Sonatype Nexus Repository Manager"
  </code></pre>
  
  <p>And desktop browsers do not. I faked the User-Agent in my Chrome browser and I got prompted for username and password. Nice! Now how to configure Nexus to always return this header?</p>