Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There's a difference between your HTTP traffic for iOS and for Android. This is guaranteed, otherwise you'd get identical behaviour from the server. The difference is probably in HTTP header(s) &amp;/or parameter(s).</p> <p>This is very difficult to debug remotely via SO Q&amp;A - E.g. we don't know what headers &amp; parameters your iOS client is successfully using nor how your server is configured &amp; programmed.</p> <p>How to diagnose the problem &amp; correct yourself:</p> <ol> <li>Trace your working HTTP traffic: iOS client &lt;-> server</li> <li>Trace your non-working HTTP traffic: Android client &lt;-> server</li> <li>Compare (2) and (3). For the most thorough comparison, save each HTTP request and response message as a separate file for (2) and (3), then <code>diff</code> the corresponding files.</li> </ol> <p>Recommended HTTP tracing tools:</p> <ul> <li><a href="http://fiddler2.com/" rel="nofollow">Fiddler2</a> (windows only) See also <a href="http://fiddler2.com/documentation/Configure-Fiddler/Tasks/ConfigureFiddler" rel="nofollow">Documentation</a></li> <li><a href="http://www.portswigger.net/burp/downloadfree.html" rel="nofollow">Burp</a> (JVM-based: windows, linux, OSX, etc) See also <a href="http://www.portswigger.net/burp/help/suite_gettingstarted.html" rel="nofollow">Getting Started</a></li> <li><a href="https://www.owasp.org/index.php/Category%3aOWASP_WebScarab_Project" rel="nofollow">WebScarab</a> (JVM-based: windows, linux, OSX, etc) See also <a href="https://www.owasp.org/index.php/WebScarab_Getting_Started" rel="nofollow">Getting Started</a></li> </ul> <p><strong>UPDATE</strong></p> <p>Seems you have the same problem for both GET and POST: the server is configured for BASIC authentication, but the client is not following the authentication protocol correctly. I think it just shows as a slightly different sympton in the two cases: for GET it says 'resource not found' (because you're not authenticated) and for POST the resource is <em>given by you</em>, but the server says you're not authorized to change the resource on the server. I suggest you've done enough (good!) debugging of request contents and now you should stop and focus on getting authentication working.</p> <ol> <li>Send you GET/POST request to the server <em>without</em> <code>Authorization</code> header</li> <li>Allow the server to prompt you for authentication with a 401 response with an <code>WWW-Authenticate</code> header containing a challenge string (e.g. <code>WWW-Authenticate: Basic realm="Protected"</code> see <a href="http://repository.root-me.org/Exploitation%20-%20Web/EN%20-%20HTTP%20basic%20authentication%20and%20digest%20authentication.pdf" rel="nofollow">RFC 2617 HTTP Basic Authentication and Digest Authentication</a>)</li> <li>Now send an additional GET request to server that (either without/with the original request contents), but includes the Authentication header, with Base 64 encoded username:password (<code>Authorization: Basic ZnJhbms6ZmllZGxlcg==</code>)</li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload