HTTP Status Code 404, 405, 407 RRS feed

  • Question

  • Hi,

    I have an application that uses ActiveSync to synchronize folder content. I would like to ask what the expected behaviors when the client receives the following HTTP statuses when sending a SYNC command request to server:

    • 404
    • 405
    • 407

    The document only covers limited number of HTTP error statuses and does not mention what the client is supposed to do.

    I would greatly appreciate any help.


    Thursday, April 5, 2018 1:46 PM

All replies

  • Hello sleung496

    Thank you for your question. One of the Open Specifications support team members will reply shortly to assist you with this issue.


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Thursday, April 5, 2018 3:35 PM
  • Hi sleung496, 

    I'll look into this and get back to you with information. 

    Best regards,
    Tom Jebo 
    Sr Escalation Engineer
    Microsoft Open Specifications Support
    Thursday, April 5, 2018 5:13 PM
  • Hi sleung496, 

    [MS-ASHTTP] "Handling a Failed Response" states: 

    "All other HTTP status codes that indicate a failed request are interpreted and handled as specified in [RFC2616]"

    In [RFC2616], the following are listed: 

    10.4.5 404 Not Found

       The server has not found anything matching the Request-URI. No
       indication is given of whether the condition is temporary or
       permanent. The 410 (Gone) status code SHOULD be used if the server
       knows, through some internally configurable mechanism, that an old
       resource is permanently unavailable and has no forwarding address.
       This status code is commonly used when the server does not wish to
       reveal exactly why the request has been refused, or when no other
       response is applicable.

    10.4.6 405 Method Not Allowed

       The method specified in the Request-Line is not allowed for the
       resource identified by the Request-URI. The response MUST include an
       Allow header containing a list of valid methods for the requested


    10.4.8 407 Proxy Authentication Required

       This code is similar to 401 (Unauthorized), but indicates that the
       client must first authenticate itself with the proxy. The proxy MUST
       return a Proxy-Authenticate header field (section 14.33) containing a
       challenge applicable to the proxy for the requested resource. The
       client MAY repeat the request with a suitable Proxy-Authorization
       header field (section 14.34). HTTP access authentication is explained
       in "HTTP Authentication: Basic and Digest Access Authentication"

    404 seems somewhat obvious in that the URI is likely malformed or just incorrect. 405 should also be self explanatory in that the client should check the allowed methods in the response. 407 applies to a proxy and relies on the Proxy-Authenticate header upon which the client can take action. 

    Let me know if you have more questions about this with respect to the [MS-ASHTTP] protocol specification.


    Monday, April 9, 2018 2:35 AM