none
ActiveSync server returning a 200 OK to http OPTIONS command when mailbox is not located on that server. RRS feed

  • Question

  • Hello,

    When I send a OPTIONS http request to a ActiveSync server, I am receiving a 200 OK response.  When I send a FolderSync command on the same tcp connection, I receive a 451 response with the X-MS-Location header pointed to a different server.

    I usually see a 451 response from an OPTIONS command when the user's mailbox is not located on that server.  My question is what exchange server setting controls whether a 200 or 451 is sent in response to a http OPTIONS request?

    Friday, July 14, 2017 10:36 PM

All replies

  • Hello pcardh0:

    Thank you for your inquiry about Microsoft office specification. We have created an incident for investigating this issue. I'm researching this for you and will get back as soon as I've an answer.

    Thanks.


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team



    Saturday, July 15, 2017 5:33 AM
  • Hello Tarun,

    Thank you for taking a look at this.  Is there an incident number for tracking this issue?

    Thanks again

    Monday, July 17, 2017 8:22 PM
  • Hello pcardh0:

    There are few conditions where exchange server can return 451 redirection error. I'm listing few here - 

    https://blogs.technet.microsoft.com/exchange/2015/03/23/exchange-activesync-on-boarding-to-office-365/

    https://technet.microsoft.com/en-us/library/dd439372(v=exchg.80).aspx

    https://msdn.microsoft.com/en-us/library/gg651019%28v=exchg.80%29.aspx?f=255&MSPPError=-2147217396

    In general this error is returned if server can't access users' mailbox or exchange server may have found efficient/better path /URL/front end server the device should be using to connect.

    Thanks


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Monday, July 17, 2017 8:46 PM
  • Hi Tarun,

    Thank you for your response.  The problem I am seeing is that the OPTIONS command is returning 200 Status Code and the FolderSync is returning a 451 Code Status.  This is for a mailbox that is not located on the ActiveSync server.  Usually when the user's mailbox is not located on the ActiveSync server, the OPTIONS command will return a 451 Status Code and a X-MS-Location containing a redirection URL.

    At this particular customer, I am not seeing this behavior, the OPTIONS command is return a 200 Status Code, but the FolderSync command is returning a 451 Status Code.

    My question is there an Exchange Server setting or configuration that controls the Status Code returned by the OPTIONS command?

    Thanks

    Tuesday, July 18, 2017 1:22 AM
  • Hello pcardh0

    Thanks for the additional details. Are you implementing the client side based on office open specifications or is this behavior being observed between outlook client and exchange server?

    Regards


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team


    Tuesday, July 18, 2017 2:53 AM
  • Hello Tarun,

    Our software is a proxy between the outlook client and the exchange server(s), we see the behavior when forwarding an OPTIONS request to the Exchange server. 

    As I mentioned the OPTIONS request and the FolderSync command are sent on the same TCP connection.  Usually we get a 451 response from the OPTIONS request when the mailbox is not located on the exchange server. 

    Regards

    Tuesday, July 18, 2017 6:24 PM
  • Hello pcardh0

    Thank you for the details.

    As I understand, the actual issue is as to why OPTIONS request is getting 200 when the mailbox is not located on the exchange server to which TCP connection is established. Let me research further and get back.

    Thanks. 


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, July 18, 2017 8:17 PM
  • Hello pcardh0

    Per our analysis; there is no setting/configuration to control whether a 451 is returned via an OPTIONS command. The client should be prepared a 451 as a response to any request and change the base URL for future requests to the value from X-MS-Location header in the response.

    Thanks.


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team


    Saturday, July 22, 2017 2:01 AM