RCA: Testing of the OPTIONS command failed

syncgw.com 1 Reputation point
2022-09-11T09:41:54.267+00:00

Hi,
we use RCA to test our ActiveSync server. Recently we got the following error. This is really strange, since test passed multiple times and compared to trace data the response from our server is exactly the same as send before:

The Microsoft Remote Connectivity Analyzer assumes our server is sending the following HTTP response headers:

Pragma: no-cache   
Allow:OPTIONS   
Allow: POST   
Public: OPTIONS, POST   
MS-ASProtocolVersions: 2.5,12.0,12.1,14.0,14.1,16.0,16.1   
MS-ASProtocolCommands: Autodiscover,Sync,SendMail,SmartForward,SmartReply,GetAttachment,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Search,Settings,Ping,ItemOperations,Provision,ResolveRecipients,Find,GetHierarchy Strict-Transport-Security: max-age=31536000   
Content-Length: 0   
Cache-Control: no-store   
Cache-Control: no-cache   
Cache-Control: must-revalidate   
Content-Type: application/vnd.ms-sync.wbxml   
Date: Sun, 11 Sep 2022 08:50:16 GMT   
Expires: Thu, 19 Nov 1981 08:52:00 GMT   
Set-Cookie: roundcube_sessid=9070757ab1b0a36ced98f2d865112a29; path=/; secure; HttpOnly   
Server: Apache   
  

The only strange thing is "Expires" header. We did not send it, but we added it. Then we tried again to send

Response: HTTP/1.1 200 Ok  
Allow: OPTIONS, POST  
Public: OPTIONS, POST  
Content-Type: application/vnd.ms-sync.wbxml  
MS-ASProtocolVersions: 2.5,12.0,12.1,14.0,14.1,16.0,16.1  
MS-ASProtocolCommands: Autodiscover,Sync,SendMail,SmartForward,SmartReply,GetAttachment,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Search,Settings,Ping,ItemOperations,Provision,ResolveRecipients,Find,GetHierarchy  
Content-Length: 0  
Date: Sun, 11 Sep 2022 08:54:51 GMT  
Expires: Sun, 11 Sep 2022 09:11:31 GMT  

This is still not accepted by RCA. Everything should be according to [MS-ASHTTP].

Any hints?

Exchange | Exchange Server | Management
{count} votes

1 answer

Sort by: Most helpful
  1. syncgw.com 1 Reputation point
    2022-09-12T10:19:46.437+00:00

    @Joy Zhang-MSFT

    Hi,
    thank you for trying to provide help. Out server is NOT an Exchange server. This is an implementation of a ActiveSync server in PHP. And we found the bug our self. Server was not sending back the "MS-Server-ActiveSync" header. Fixing that, the conformance test passed successfully.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.