title: Accessing our web app on the stock Android 4.1 and 4.2 browser
body: <p>So I am currently having this problem of trying to open up our web app on the official stock Android browser for Jelly Bean. I don't know how well I can elaborate this problem, but I will try my best.</p>
  
  <p>For devices that run ICS or older, on any browser (stock, firefox, chrome) we can type in the URL for our web app, get taken to the login page, login, and view everything fine.</p>
  
  <p>For devices that run Jelly Bean (4.1 and 4.2), if we type in the url into the <strong>stock browser</strong>, we get the following:</p>
  
  <p><img src="https://i.stack.imgur.com/cj8HF.png" alt="enter image description here"> </p>
  
  <p>However, if we use <strong>Chrome</strong> or <strong>Firefox</strong>, its fine. </p>
  
  <p>It's odd that we get this error because I am already authenticated on our network, and I only try to access the login screen so no other authentication would be required. </p>
  
  <p>Our web app grabs information from a server, and it doesn't seem to be a problem on the server side.</p>
  
  <p>So it seems like the culprit is the stock browser in Jelly Bean, and I tried looking up if there were any changes to the stock web browser from ICS to Jelly Bean, but I couldn't find anything yet.</p>
  
  <p>Has anybody come up with an issue like this, or is aware of any big changes (maybe related to security?) that were made to the stock android browser on Jelly Bean?</p>
  
  <p>EDIT: This web app is not available externally. Currently we have only tested internally where you would have to be connected to our internal network.</p>
  
  <p>EDIT2: Just checked with Dolphin Browser and the same thing happened... so I'm really lost now as I am even less sure that it has something to do with the 4.1+ stock browsers. Also, something else that makes me feel even more lost is that, I just checked on the galaxy SIII's stock browser on 4.1.2 and the page loads fine...</p>
  
  <p>EDIT3: Good news, further investigation has been done by our devs and apparently this is the problem:</p>
  
  <blockquote>
    <p>the default browser adds an extra header to the request that makes our server think it is an ajax request and rejects it because the rest of the request is not actually an ajax request... This bug is caused because the default browser in Android 4.1+ has added a new header to all requests "X-Requested-With: com.android.browser".</p>
  </blockquote>
  
  <p>So I'm guessing the Dolphin HD browser does this as well... further investigation is being done so will get back to this and put up an answer </p>